From Michael.Zimmer at federalmogul.com Mon May 2 08:14:53 2016 From: Michael.Zimmer at federalmogul.com (Zimmer, Michael) Date: Mon, 2 May 2016 13:14:53 +0000 Subject: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source In-Reply-To: <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> References: , , <6763936ED419A949BE5DEAA5A345C7224CF6EB93@sfldmiex022> <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> Message-ID: <6763936ED419A949BE5DEAA5A345C7224CF6ED05@sfldmiex022> Stuart, I'm looking in the ODBC administration window but cannot seem to find the appropriate menu for the quoted identifiers. Could you point me in the right direction? Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, April 29, 2016 7:06 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The OBDC DSN should contain a parameter "Use ANSI Quoted Identifiers:" Set it to Yes and No and see what happens. On 29 Apr 2016 at 18:33, Zimmer, Michael wrote: > > NOW here's what's really weird: On the four, identically set-up PCs > we run this Excel sheet on -- only one can successfully change > criteria and have the query work, the other three all can successfully > use the spreadsheet, but cannot adjust any criteria in the query. > > So the error message says that SQL doesn't like the single '' marks > for the alias we want to use. But I'm thinking that it might be some > setting I'm missing in the ODBC administration, maybe something in the > Conversions or CCSID? > > Mike > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From Michael.Zimmer at federalmogul.com Mon May 2 09:18:00 2016 From: Michael.Zimmer at federalmogul.com (Zimmer, Michael) Date: Mon, 2 May 2016 14:18:00 +0000 Subject: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source In-Reply-To: <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> References: , , <6763936ED419A949BE5DEAA5A345C7224CF6EB93@sfldmiex022> <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> Message-ID: <6763936ED419A949BE5DEAA5A345C7224CF6ED4A@sfldmiex022> Ouch! Monday morning brain reboot needed. Found the ODBC DSN in the ODBC Create New Data Source wizard. "Use ANSI Quoted Identifiers" checked on by default. Unchecked = no change "Use ANSI nulls, padding's and warnings" checked on by default. Unchecked = no change I tried various combinations of the above all with no change to problem. Then I unchecked the "Perform translation for character data" box to see if that would help. = no change. Still stumped in Wisconsin. Ugh! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, April 29, 2016 7:06 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The OBDC DSN should contain a parameter "Use ANSI Quoted Identifiers:" Set it to Yes and No and see what happens. On 29 Apr 2016 at 18:33, Zimmer, Michael wrote: > > NOW here's what's really weird: On the four, identically set-up PCs > we run this Excel sheet on -- only one can successfully change > criteria and have the query work, the other three all can successfully > use the spreadsheet, but cannot adjust any criteria in the query. > > So the error message says that SQL doesn't like the single '' marks > for the alias we want to use. But I'm thinking that it might be some > setting I'm missing in the ODBC administration, maybe something in the > Conversions or CCSID? > > Mike > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From scott.marcus at tsstech.com Mon May 2 10:40:06 2016 From: scott.marcus at tsstech.com (Scott Marcus) Date: Mon, 2 May 2016 11:40:06 -0400 Subject: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source In-Reply-To: <6763936ED419A949BE5DEAA5A345C7224CF6ED4A@sfldmiex022> References: , , <6763936ED419A949BE5DEAA5A345C7224CF6EB93@sfldmiex022> <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> <6763936ED419A949BE5DEAA5A345C7224CF6ED4A@sfldmiex022> Message-ID: Did you try renaming one field at a time? It could be that one field is causing this issue. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Zimmer, Michael Sent: Monday, May 2, 2016 10:18 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Ouch! Monday morning brain reboot needed. Found the ODBC DSN in the ODBC Create New Data Source wizard. "Use ANSI Quoted Identifiers" checked on by default. Unchecked = no change "Use ANSI nulls, padding's and warnings" checked on by default. Unchecked = no change I tried various combinations of the above all with no change to problem. Then I unchecked the "Perform translation for character data" box to see if that would help. = no change. Still stumped in Wisconsin. Ugh! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, April 29, 2016 7:06 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The OBDC DSN should contain a parameter "Use ANSI Quoted Identifiers:" Set it to Yes and No and see what happens. On 29 Apr 2016 at 18:33, Zimmer, Michael wrote: > > NOW here's what's really weird: On the four, identically set-up PCs > we run this Excel sheet on -- only one can successfully change > criteria and have the query work, the other three all can successfully > use the spreadsheet, but cannot adjust any criteria in the query. > > So the error message says that SQL doesn't like the single '' marks > for the alias we want to use. But I'm thinking that it might be some > setting I'm missing in the ODBC administration, maybe something in the > Conversions or CCSID? > > Mike > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com NOTICE: This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited. If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected. Any information included in this email is provided on an ?as is? and ?where as? basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email. From scott.marcus at tsstech.com Mon May 2 10:54:51 2016 From: scott.marcus at tsstech.com (Scott Marcus) Date: Mon, 2 May 2016 11:54:51 -0400 Subject: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source In-Reply-To: References: , , <6763936ED419A949BE5DEAA5A345C7224CF6EB93@sfldmiex022> <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> <6763936ED419A949BE5DEAA5A345C7224CF6ED4A@sfldmiex022> Message-ID: I would start checking what is different with the working vs. non-working pc's. This would include Windows versions, ODBC driver versions, Excel versions, MS Office options that were used during installation, installed software, Windows updates(this is huge task so leave it for last efforts), etc.. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Scott Marcus Sent: Monday, May 2, 2016 11:40 AM To: 'Discussion concerning MS SQL Server' Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Did you try renaming one field at a time? It could be that one field is causing this issue. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Zimmer, Michael Sent: Monday, May 2, 2016 10:18 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Ouch! Monday morning brain reboot needed. Found the ODBC DSN in the ODBC Create New Data Source wizard. "Use ANSI Quoted Identifiers" checked on by default. Unchecked = no change "Use ANSI nulls, padding's and warnings" checked on by default. Unchecked = no change I tried various combinations of the above all with no change to problem. Then I unchecked the "Perform translation for character data" box to see if that would help. = no change. Still stumped in Wisconsin. Ugh! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, April 29, 2016 7:06 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The OBDC DSN should contain a parameter "Use ANSI Quoted Identifiers:" Set it to Yes and No and see what happens. On 29 Apr 2016 at 18:33, Zimmer, Michael wrote: > > NOW here's what's really weird: On the four, identically set-up PCs > we run this Excel sheet on -- only one can successfully change > criteria and have the query work, the other three all can successfully > use the spreadsheet, but cannot adjust any criteria in the query. > > So the error message says that SQL doesn't like the single '' marks > for the alias we want to use. But I'm thinking that it might be some > setting I'm missing in the ODBC administration, maybe something in the > Conversions or CCSID? > > Mike > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com NOTICE: This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited. If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected. Any information included in this email is provided on an ?as is? and ?where as? basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From Michael.Zimmer at federalmogul.com Mon May 2 11:02:35 2016 From: Michael.Zimmer at federalmogul.com (Zimmer, Michael) Date: Mon, 2 May 2016 16:02:35 +0000 Subject: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source In-Reply-To: References: , , <6763936ED419A949BE5DEAA5A345C7224CF6EB93@sfldmiex022> <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> <6763936ED419A949BE5DEAA5A345C7224CF6ED4A@sfldmiex022> Message-ID: <6763936ED419A949BE5DEAA5A345C7224CF6EFCD@sfldmiex022> Yep, I did change only one variable at a time and worked my way through each variable. I guess now I'll have to put the two laptops side by side and start looking for differences in set-up etc. This is a lot of work just to get column names changed! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Scott Marcus Sent: Monday, May 02, 2016 10:40 AM To: 'Discussion concerning MS SQL Server' Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Did you try renaming one field at a time? It could be that one field is causing this issue. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Zimmer, Michael Sent: Monday, May 2, 2016 10:18 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Ouch! Monday morning brain reboot needed. Found the ODBC DSN in the ODBC Create New Data Source wizard. "Use ANSI Quoted Identifiers" checked on by default. Unchecked = no change "Use ANSI nulls, padding's and warnings" checked on by default. Unchecked = no change I tried various combinations of the above all with no change to problem. Then I unchecked the "Perform translation for character data" box to see if that would help. = no change. Still stumped in Wisconsin. Ugh! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, April 29, 2016 7:06 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The OBDC DSN should contain a parameter "Use ANSI Quoted Identifiers:" Set it to Yes and No and see what happens. On 29 Apr 2016 at 18:33, Zimmer, Michael wrote: > > NOW here's what's really weird: On the four, identically set-up PCs > we run this Excel sheet on -- only one can successfully change > criteria and have the query work, the other three all can successfully > use the spreadsheet, but cannot adjust any criteria in the query. > > So the error message says that SQL doesn't like the single '' marks > for the alias we want to use. But I'm thinking that it might be some > setting I'm missing in the ODBC administration, maybe something in the > Conversions or CCSID? > > Mike > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com NOTICE: This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited. If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected. Any information included in this email is provided on an ?as is? and ?where as? basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From scott.marcus at tsstech.com Mon May 2 11:35:46 2016 From: scott.marcus at tsstech.com (Scott Marcus) Date: Mon, 2 May 2016 12:35:46 -0400 Subject: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source In-Reply-To: <6763936ED419A949BE5DEAA5A345C7224CF6EFCD@sfldmiex022> References: , , <6763936ED419A949BE5DEAA5A345C7224CF6EB93@sfldmiex022> <5723F703.13081.27C93E77@stuart.lexacorp.com.pg> <6763936ED419A949BE5DEAA5A345C7224CF6ED4A@sfldmiex022> <6763936ED419A949BE5DEAA5A345C7224CF6EFCD@sfldmiex022> Message-ID: The older the database the more incompatible with new OS's and software. I run into these same kind of issues with an old Oracle 8i system. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Zimmer, Michael Sent: Monday, May 2, 2016 12:03 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Yep, I did change only one variable at a time and worked my way through each variable. I guess now I'll have to put the two laptops side by side and start looking for differences in set-up etc. This is a lot of work just to get column names changed! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Scott Marcus Sent: Monday, May 02, 2016 10:40 AM To: 'Discussion concerning MS SQL Server' Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Did you try renaming one field at a time? It could be that one field is causing this issue. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Zimmer, Michael Sent: Monday, May 2, 2016 10:18 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Ouch! Monday morning brain reboot needed. Found the ODBC DSN in the ODBC Create New Data Source wizard. "Use ANSI Quoted Identifiers" checked on by default. Unchecked = no change "Use ANSI nulls, padding's and warnings" checked on by default. Unchecked = no change I tried various combinations of the above all with no change to problem. Then I unchecked the "Perform translation for character data" box to see if that would help. = no change. Still stumped in Wisconsin. Ugh! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, April 29, 2016 7:06 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The OBDC DSN should contain a parameter "Use ANSI Quoted Identifiers:" Set it to Yes and No and see what happens. On 29 Apr 2016 at 18:33, Zimmer, Michael wrote: > > NOW here's what's really weird: On the four, identically set-up PCs > we run this Excel sheet on -- only one can successfully change > criteria and have the query work, the other three all can successfully > use the spreadsheet, but cannot adjust any criteria in the query. > > So the error message says that SQL doesn't like the single '' marks > for the alias we want to use. But I'm thinking that it might be some > setting I'm missing in the ODBC administration, maybe something in the > Conversions or CCSID? > > Mike > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com NOTICE: This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited. If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected. Any information included in this email is provided on an ?as is? and ?where as? basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From accessd at shaw.ca Mon May 2 12:02:40 2016 From: accessd at shaw.ca (Jim Lawrence) Date: Mon, 2 May 2016 11:02:40 -0600 (MDT) Subject: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source In-Reply-To: Message-ID: <2054342916.16158332.1462208560565.JavaMail.root@shaw.ca> I can so relate... My solution was to only use ADO as the universal connector. Because its an open and industry standard, has been around for almost twenty years, is very mature, backward compatible, still under full development and it has been built into Microsoft Windows since the '90s. I have used this protocol with MS products and Oracle (from 6.x to 11.x) for years. (When working on contract for the government, three sets of books lined my book shelf...various Microsoft tech manuals, a host of Oracle course manuals and few books about ADO.) Jim ----- Original Message ----- From: "Scott Marcus" To: "Discussion concerning MS SQL Server" Sent: Monday, May 2, 2016 9:35:46 AM Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The older the database the more incompatible with new OS's and software. I run into these same kind of issues with an old Oracle 8i system. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Zimmer, Michael Sent: Monday, May 2, 2016 12:03 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Yep, I did change only one variable at a time and worked my way through each variable. I guess now I'll have to put the two laptops side by side and start looking for differences in set-up etc. This is a lot of work just to get column names changed! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Scott Marcus Sent: Monday, May 02, 2016 10:40 AM To: 'Discussion concerning MS SQL Server' Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Did you try renaming one field at a time? It could be that one field is causing this issue. -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Zimmer, Michael Sent: Monday, May 2, 2016 10:18 AM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source Ouch! Monday morning brain reboot needed. Found the ODBC DSN in the ODBC Create New Data Source wizard. "Use ANSI Quoted Identifiers" checked on by default. Unchecked = no change "Use ANSI nulls, padding's and warnings" checked on by default. Unchecked = no change I tried various combinations of the above all with no change to problem. Then I unchecked the "Perform translation for character data" box to see if that would help. = no change. Still stumped in Wisconsin. Ugh! Mike -----Original Message----- From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, April 29, 2016 7:06 PM To: Discussion concerning MS SQL Server Subject: Re: [dba-SQLServer] SQL error in Excel query to IBM DB2 data source The OBDC DSN should contain a parameter "Use ANSI Quoted Identifiers:" Set it to Yes and No and see what happens. On 29 Apr 2016 at 18:33, Zimmer, Michael wrote: > > NOW here's what's really weird: On the four, identically set-up PCs > we run this Excel sheet on -- only one can successfully change > criteria and have the query work, the other three all can successfully > use the spreadsheet, but cannot adjust any criteria in the query. > > So the error message says that SQL doesn't like the single '' marks > for the alias we want to use. But I'm thinking that it might be some > setting I'm missing in the ODBC administration, maybe something in the > Conversions or CCSID? > > Mike > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com NOTICE: This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited. If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected. Any information included in this email is provided on an ?as is? and ?where as? basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com