I used the following SQL to extract data from our Firms emplyee database and
creates a text file that gets imported into our copy machine controllers.
Output lines look like this:
A|U|4111|MPLS, PBMS|01|0||
A|U|4222|RIC, PBMS|06|0||
A|U|2036|user, name|01|0|N|1234562|
The last number is the last 7 of the persons corporate VISA card. On SQL
2000 this SQL worked:
select 'A|U|' +
RTRIM(EMPLOYEE_CODE) + '|'
+ RTRIM(EMPLOYEE_NAME) + '|'
+ rtrim(offc) + '|0|' +
case position
when 'partner' then 'P'
else 'N'
end
+ '|' , _visano , '|'
from HBM_PERSNL
where INACTIVE = 'N'
and EMPLOYEE_NAME NOT like '%CMS%'
and EMPLOYEE_NAME NOT Like '%billing%'
and EMPLOYEE_NAME NOT Like '%temp%'
On SQL 2005 it doesn't: The sql runs but only delivers those with that
VISA Numeber, where it use to give you both those with and without cards.
Any Ideas?When you don't have a credit card number, are you storing a NULL instead?
Are you getting any errors? How are you creating the file?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Jay Bukstein" <JayBukstein@.discussions.microsoft.com> wrote in message
news:697B4582-6D4F-47BD-B5DF-F1AD95422D0C@.microsoft.com...
I used the following SQL to extract data from our Firms emplyee database and
creates a text file that gets imported into our copy machine controllers.
Output lines look like this:
A|U|4111|MPLS, PBMS|01|0||
A|U|4222|RIC, PBMS|06|0||
A|U|2036|user, name|01|0|N|1234562|
The last number is the last 7 of the persons corporate VISA card. On SQL
2000 this SQL worked:
select 'A|U|' +
RTRIM(EMPLOYEE_CODE) + '|'
+ RTRIM(EMPLOYEE_NAME) + '|'
+ rtrim(offc) + '|0|' +
case position
when 'partner' then 'P'
else 'N'
end
+ '|' , _visano , '|'
from HBM_PERSNL
where INACTIVE = 'N'
and EMPLOYEE_NAME NOT like '%CMS%'
and EMPLOYEE_NAME NOT Like '%billing%'
and EMPLOYEE_NAME NOT Like '%temp%'
On SQL 2005 it doesn't: The sql runs but only delivers those with that
VISA Numeber, where it use to give you both those with and without cards.
Any Ideas?|||Hi Jay
a quick question, is _visano a column in the HBM_PERSNL table?
I noticed that at the end of the query you are using a comma instead of + to
concat the string, should the query be:
select 'A|U|' +
RTRIM(EMPLOYEE_CODE) + '|'
+ RTRIM(EMPLOYEE_NAME) + '|'
+ rtrim(offc) + '|0|' +
case position
when 'partner' then 'P'
else 'N'
end
+ '|' + _visano + '|'
from HBM_PERSNL
where INACTIVE = 'N'
and EMPLOYEE_NAME NOT like '%CMS%'
and EMPLOYEE_NAME NOT Like '%billing%'
and EMPLOYEE_NAME NOT Like '%temp%'
Lucas
"Jay Bukstein" wrote:
> I used the following SQL to extract data from our Firms emplyee database a
nd
> creates a text file that gets imported into our copy machine controllers.
> Output lines look like this:
> A|U|4111|MPLS, PBMS|01|0||
> A|U|4222|RIC, PBMS|06|0||
> A|U|2036|user, name|01|0|N|1234562|
> The last number is the last 7 of the persons corporate VISA card. On SQL
> 2000 this SQL worked:
> select 'A|U|' +
> RTRIM(EMPLOYEE_CODE) + '|'
> + RTRIM(EMPLOYEE_NAME) + '|'
> + rtrim(offc) + '|0|' +
> case position
> when 'partner' then 'P'
> else 'N'
> end
> + '|' , _visano , '|'
> from HBM_PERSNL
> where INACTIVE = 'N'
> and EMPLOYEE_NAME NOT like '%CMS%'
> and EMPLOYEE_NAME NOT Like '%billing%'
> and EMPLOYEE_NAME NOT Like '%temp%'
> On SQL 2005 it doesn't: The sql runs but only delivers those with that
> VISA Numeber, where it use to give you both those with and without cards.
> Any Ideas?
>|||Sounds like your server or session defaults on '05 yield null on
concatenation; i.e., select 'a' + NULL yields NULL whereas on 2000 select
'a' + NULL yields 'a'.
Suggest to modify the query to
....
'|' + ISNULL(_visano, '') + '|'
...
In fact, this is a good practice for any columns that allow null. That way
changes to server or session settings always yield the same results.
"Jay Bukstein" <JayBukstein@.discussions.microsoft.com> wrote in message
news:697B4582-6D4F-47BD-B5DF-F1AD95422D0C@.microsoft.com...
>I used the following SQL to extract data from our Firms emplyee database
>and
> creates a text file that gets imported into our copy machine controllers.
> Output lines look like this:
> A|U|4111|MPLS, PBMS|01|0||
> A|U|4222|RIC, PBMS|06|0||
> A|U|2036|user, name|01|0|N|1234562|
> The last number is the last 7 of the persons corporate VISA card. On SQL
> 2000 this SQL worked:
> select 'A|U|' +
> RTRIM(EMPLOYEE_CODE) + '|'
> + RTRIM(EMPLOYEE_NAME) + '|'
> + rtrim(offc) + '|0|' +
> case position
> when 'partner' then 'P'
> else 'N'
> end
> + '|' , _visano , '|'
> from HBM_PERSNL
> where INACTIVE = 'N'
> and EMPLOYEE_NAME NOT like '%CMS%'
> and EMPLOYEE_NAME NOT Like '%billing%'
> and EMPLOYEE_NAME NOT Like '%temp%'
> On SQL 2005 it doesn't: The sql runs but only delivers those with that
> VISA Numeber, where it use to give you both those with and without cards.
> Any Ideas?
>
Showing posts with label fails. Show all posts
Showing posts with label fails. Show all posts
Monday, March 19, 2012
Friday, March 9, 2012
IIS Fails back when prevent failback is checked
Howdy,
IIS6 Win2003.
Set up the group on Node1. During testing I can down Node1 and groups
and resources failover to Node2. After Node1 comes back online, the
IIS Service Group failsback to Node1. Did I miss something?
TIA for any assistance.
Bill
Bill,
Have you set the failback policy for the group to failback immediately? The default is "prevent failback".
Additional Information:
=====================
To set group failback policy
Open Cluster Administrator.
In the console tree, click the Groups folder.
In the details pane, click the appropriate group.
On the File menu, click Properties.
On the Failback tab, click Prevent failback or Allow failback.
If you click Allow failback, then either click Immediately, or click Failback between and set the time interval.
Notes
To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of
the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.
To open Cluster Administrator, click Start, click Control Panel, double-click Administrative Tools, and then double-click Cluster Administrator.
To set the time interval for Failback between, enter numbers between 0 and 23 for the beginning and end of the interval. If the first number is greater than the second, the interval ends on the following day. The
numbers correspond to the local time of the cluster group, as read on a 24-hour clock.
It is important to set the failback time because you may not want failback to occur during hours of peak usage.
If no preferred owners are specified for the group, then failback does not occur.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam,
I have the failback property set to 'Prevent failback'. Yet the IIS
Services Group continues to 'Failback' when the Node comes back online.
It does not seem to interfere with the functionality of IIS running from
the other Node though. While looking at the properties of this Group I
did notice a differnce in the failover threshold and period. On the
other two groups the I have the Threshold set to 10 and the period set
to 6 hrs. Would this have an effect?
Thanks again,
Bill
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Bll,
Shutdown node 1 and verify that all resources come online on node 2.
If you don't want to shut down node 1 then move all resources to node 2 and pause node 1. make sure that all resources are coming online on node 2. If it fails then see the errors in NT logs and cluster.log and fix
them first.
You mentioned something about the difference in group properties? What is the difference that you saw ?
You wrote "On the other two groups the I have the Threshold set to 10 and the period set to 6 hrs. ". This is the default. What are the values on the IIS group? Did someone change it from the default?
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam,
If I down Node1, failover to Node2 works as designed no issues, when
Node1 comes back online, the IIS Services Group failsback to Node1.
There is no loss in functionality, IIS works as needed. It is just that
the Group fails back to the other Node.
I did Move the group to Node2 and it has stayed there, it is just during
failover from 1 to 2 that the anomialy occurs.
Settings were: Threshold 1, Period 2. I may have changed them some time
back (I fell off of testing for almost two months).
Thanks,
Bill
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
IIS6 Win2003.
Set up the group on Node1. During testing I can down Node1 and groups
and resources failover to Node2. After Node1 comes back online, the
IIS Service Group failsback to Node1. Did I miss something?
TIA for any assistance.
Bill
Bill,
Have you set the failback policy for the group to failback immediately? The default is "prevent failback".
Additional Information:
=====================
To set group failback policy
Open Cluster Administrator.
In the console tree, click the Groups folder.
In the details pane, click the appropriate group.
On the File menu, click Properties.
On the Failback tab, click Prevent failback or Allow failback.
If you click Allow failback, then either click Immediately, or click Failback between and set the time interval.
Notes
To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of
the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.
To open Cluster Administrator, click Start, click Control Panel, double-click Administrative Tools, and then double-click Cluster Administrator.
To set the time interval for Failback between, enter numbers between 0 and 23 for the beginning and end of the interval. If the first number is greater than the second, the interval ends on the following day. The
numbers correspond to the local time of the cluster group, as read on a 24-hour clock.
It is important to set the failback time because you may not want failback to occur during hours of peak usage.
If no preferred owners are specified for the group, then failback does not occur.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam,
I have the failback property set to 'Prevent failback'. Yet the IIS
Services Group continues to 'Failback' when the Node comes back online.
It does not seem to interfere with the functionality of IIS running from
the other Node though. While looking at the properties of this Group I
did notice a differnce in the failover threshold and period. On the
other two groups the I have the Threshold set to 10 and the period set
to 6 hrs. Would this have an effect?
Thanks again,
Bill
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Bll,
Shutdown node 1 and verify that all resources come online on node 2.
If you don't want to shut down node 1 then move all resources to node 2 and pause node 1. make sure that all resources are coming online on node 2. If it fails then see the errors in NT logs and cluster.log and fix
them first.
You mentioned something about the difference in group properties? What is the difference that you saw ?
You wrote "On the other two groups the I have the Threshold set to 10 and the period set to 6 hrs. ". This is the default. What are the values on the IIS group? Did someone change it from the default?
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam,
If I down Node1, failover to Node2 works as designed no issues, when
Node1 comes back online, the IIS Services Group failsback to Node1.
There is no loss in functionality, IIS works as needed. It is just that
the Group fails back to the other Node.
I did Move the group to Node2 and it has stayed there, it is just during
failover from 1 to 2 that the anomialy occurs.
Settings were: Threshold 1, Period 2. I may have changed them some time
back (I fell off of testing for almost two months).
Thanks,
Bill
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Subscribe to:
Posts (Atom)