From mikedorism at verizon.net Sun Oct 1 13:10:13 2006 From: mikedorism at verizon.net (Mike & Doris Manning) Date: Sun, 01 Oct 2006 14:10:13 -0400 Subject: [dba-SQLServer] Moving the log file In-Reply-To: <007301c6e30c$60305210$647aa8c0@m6805> Message-ID: <000701c6e584$d8181ae0$2f01a8c0@dorismanning> Yes, you need to click on the database name and choose Properties. You can change where the Database and Transaction Log files get stored from tabs on this screen. Doris Manning mikedorism at verizon.net -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, September 28, 2006 10:43 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Moving the log file Is there a way to have SQL Server itself move it's log file to another drive? I created a database and it creates the log file in the same directory as the data file. If I detach the database and physically move the log file, SQL Server refuses to allow me to attach the database again using (changing the location of) the log file on the other drive. If I just click OK with the little red X in the log file location, it creates a new log file back in the same location as the data file. John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Sun Oct 1 14:42:02 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Sun, 1 Oct 2006 15:42:02 -0400 Subject: [dba-SQLServer] Moving the log file In-Reply-To: <000701c6e584$d8181ae0$2f01a8c0@dorismanning> Message-ID: <002401c6e591$abde2980$647aa8c0@m6805> Yes, but HOW? I tried copying and then editing the location in that screen and it refused to accept the edit. I have managed it in the past but never really discovered the magic incantation to cause it to happen whenever I want, rather than whenever it decided to cooperate. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike & Doris Manning Sent: Sunday, October 01, 2006 2:10 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Moving the log file Yes, you need to click on the database name and choose Properties. You can change where the Database and Transaction Log files get stored from tabs on this screen. Doris Manning mikedorism at verizon.net -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Thursday, September 28, 2006 10:43 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Moving the log file Is there a way to have SQL Server itself move it's log file to another drive? I created a database and it creates the log file in the same directory as the data file. If I detach the database and physically move the log file, SQL Server refuses to allow me to attach the database again using (changing the location of) the log file on the other drive. If I just click OK with the little red X in the log file location, it creates a new log file back in the same location as the data file. John W. Colby Colby Consulting www.ColbyConsulting.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 From fhtapia at gmail.com Sun Oct 1 20:54:45 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Sun, 1 Oct 2006 18:54:45 -0700 Subject: [dba-SQLServer] Moving the log file In-Reply-To: <002401c6e591$abde2980$647aa8c0@m6805> References: <000701c6e584$d8181ae0$2f01a8c0@dorismanning> <002401c6e591$abde2980$647aa8c0@m6805> Message-ID: If you are attaching the DB it's like this >From Query Analyzer RESTORE DATABASE devREDe FROM DISK = 'D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\DB.bak' WITH MOVE 'myDB_log' TO 'D:\Program Files\Microsoft SQL Server\MSSQL\DATA\DB_log.ldf' >From EM: When creating a new database, the 3rd tab is for the transaction log simply choose an availalbe path on your sql server. Click the ellipses (three dots) and viola... click and choose the drive/folder that you want your transaction log to be at. On 10/1/06, JWColby wrote: > Yes, but HOW? I tried copying and then editing the location in that screen > and it refused to accept the edit. I have managed it in the past but never > really discovered the magic incantation to cause it to happen whenever I > want, rather than whenever it decided to cooperate. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike & > Doris Manning > Sent: Sunday, October 01, 2006 2:10 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Moving the log file > > Yes, you need to click on the database name and choose Properties. You can > change where the Database and Transaction Log files get stored from tabs on > this screen. > > Doris Manning > mikedorism at verizon.net > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby > Sent: Thursday, September 28, 2006 10:43 AM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] Moving the log file > > Is there a way to have SQL Server itself move it's log file to another > drive? I created a database and it creates the log file in the same > directory as the data file. If I detach the database and physically move > the log file, SQL Server refuses to allow me to attach the database again > using (changing the location of) the log file on the other drive. If I just > click OK with the little red X in the log file location, it creates a new > log file back in the same location as the data file. > > > John W. Colby > Colby Consulting > www.ColbyConsulting.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 > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From jwcolby at colbyconsulting.com Mon Oct 2 08:02:23 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 2 Oct 2006 09:02:23 -0400 Subject: [dba-SQLServer] Moving the log file In-Reply-To: Message-ID: <003501c6e623$0188bc60$647aa8c0@m6805> Francisco, the "RESTORE" did not work because this is not a backup file, it is just a database that was detached. I know how to do it for creating a new one but these are files already in existence that I just need to move around as my system changes. So I still don't know how to "move" a log file from one disk to another that was just detached (or not detached if necessary). John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Sunday, October 01, 2006 9:55 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Moving the log file If you are attaching the DB it's like this >From Query Analyzer RESTORE DATABASE devREDe FROM DISK = 'D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\DB.bak' WITH MOVE 'myDB_log' TO 'D:\Program Files\Microsoft SQL Server\MSSQL\DATA\DB_log.ldf' >From EM: When creating a new database, the 3rd tab is for the transaction log simply choose an availalbe path on your sql server. Click the ellipses (three dots) and viola... click and choose the drive/folder that you want your transaction log to be at. On 10/1/06, JWColby wrote: > Yes, but HOW? I tried copying and then editing the location in that > screen and it refused to accept the edit. I have managed it in the > past but never really discovered the magic incantation to cause it to > happen whenever I want, rather than whenever it decided to cooperate. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike > & Doris Manning > Sent: Sunday, October 01, 2006 2:10 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Moving the log file > > Yes, you need to click on the database name and choose Properties. > You can change where the Database and Transaction Log files get stored > from tabs on this screen. > > Doris Manning > mikedorism at verizon.net > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > JWColby > Sent: Thursday, September 28, 2006 10:43 AM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] Moving the log file > > Is there a way to have SQL Server itself move it's log file to another > drive? I created a database and it creates the log file in the same > directory as the data file. If I detach the database and physically > move the log file, SQL Server refuses to allow me to attach the > database again using (changing the location of) the log file on the > other drive. If I just click OK with the little red X in the log file > location, it creates a new log file back in the same location as the data file. > > > John W. Colby > Colby Consulting > www.ColbyConsulting.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 > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From rlavsa at tigg.com Mon Oct 2 08:12:54 2006 From: rlavsa at tigg.com (Richard Lavsa) Date: Mon, 2 Oct 2006 09:12:54 -0400 Subject: [dba-SQLServer] DTS Conditional email In-Reply-To: <092820062015.13480.451C2D69000C8AF3000034A8219792676103010CD2079C080C03BF969B019607080C@mchsi.com> Message-ID: Ron, Thanks for the idea. I got hung up last week with another issue but wanted to let you know I it working this morning.. =).. Rich -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Ron Allen Sent: Thursday, September 28, 2006 4:16 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] DTS Conditional email I have to do something similar. In my case, I store the number of rows returned in a global variable, then I use an ActiveX script in DTS to branch execution based on the value. Here is the JavaScript I use: function Main() { if (DTSGlobalVariables("RecordCount").value == 0) { return(DTSTaskExecResult_Failure); } else { return(DTSTaskExecResult_Success); } } Then I just branch on failure to the steps needed for that, and on success to the rest of the DTS package that runs normally. HTH, Ron > Hello all, > > I was able to build a workflow very quickly to run a query, get the > results, export them into an excel file, then email the file to a > distribution list. > > I am stuck on how to make it do this only when the query returns rows. > The reason for this to be conditional, is that this only happens when > a process does not complete of which then needs to throw a flag to > certain people to check into the issue. > > Any help would be greatly appreciated. > > Rich > CONFIDENTIALITY NOTICE: The information contained in this transmission > may be confidential or privileged, and is intended solely for the > entity or individual to whom it is addressed. If you are not the > intended recipient, please be advised that any use, copying, > disclosure, dissemination or distribution is strictly prohibited. If > you received this transmission in error, please contact the sender at > TIGG Corporation immediately by replying to this email and deleting it from your computer. > _______________________________________________ > 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 CONFIDENTIALITY NOTICE: The information contained in this transmission may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please be advised that any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you received this transmission in error, please contact the sender at TIGG Corporation immediately by replying to this email and deleting it from your computer. From mwp.reid at qub.ac.uk Mon Oct 2 08:23:08 2006 From: mwp.reid at qub.ac.uk (Martin Reid) Date: Mon, 2 Oct 2006 14:23:08 +0100 Subject: [dba-SQLServer] Moving the log file References: <003501c6e623$0188bc60$647aa8c0@m6805> Message-ID: John have you tried this http://www.sql-server-performance.com/q&a34.asp Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of JWColby Sent: Mon 02/10/2006 14:02 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Moving the log file Francisco, the "RESTORE" did not work because this is not a backup file, it is just a database that was detached. I know how to do it for creating a new one but these are files already in existence that I just need to move around as my system changes. So I still don't know how to "move" a log file from one disk to another that was just detached (or not detached if necessary). John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Sunday, October 01, 2006 9:55 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Moving the log file If you are attaching the DB it's like this >From Query Analyzer RESTORE DATABASE devREDe FROM DISK = 'D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\DB.bak' WITH MOVE 'myDB_log' TO 'D:\Program Files\Microsoft SQL Server\MSSQL\DATA\DB_log.ldf' >From EM: When creating a new database, the 3rd tab is for the transaction log simply choose an availalbe path on your sql server. Click the ellipses (three dots) and viola... click and choose the drive/folder that you want your transaction log to be at. On 10/1/06, JWColby wrote: > Yes, but HOW? I tried copying and then editing the location in that > screen and it refused to accept the edit. I have managed it in the > past but never really discovered the magic incantation to cause it to > happen whenever I want, rather than whenever it decided to cooperate. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Mike > & Doris Manning > Sent: Sunday, October 01, 2006 2:10 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Moving the log file > > Yes, you need to click on the database name and choose Properties. > You can change where the Database and Transaction Log files get stored > from tabs on this screen. > > Doris Manning > mikedorism at verizon.net > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > JWColby > Sent: Thursday, September 28, 2006 10:43 AM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] Moving the log file > > Is there a way to have SQL Server itself move it's log file to another > drive? I created a database and it creates the log file in the same > directory as the data file. If I detach the database and physically > move the log file, SQL Server refuses to allow me to attach the > database again using (changing the location of) the log file on the > other drive. If I just click OK with the little red X in the log file > location, it creates a new log file back in the same location as the data file. > > > John W. Colby > Colby Consulting > www.ColbyConsulting.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 > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 shait at mindspring.com Mon Oct 2 08:36:47 2006 From: shait at mindspring.com (Stephen Hait) Date: Mon, 2 Oct 2006 09:36:47 -0400 Subject: [dba-SQLServer] Moving the log file In-Reply-To: <003501c6e623$0188bc60$647aa8c0@m6805> References: <003501c6e623$0188bc60$647aa8c0@m6805> Message-ID: > So I still don't know how to "move" a log file from one disk to another that > was just detached (or not detached if necessary). See if this helps: EXEC sp_attach_db @dbname = N'yourdbname', @filename1 = N'\\yourserver\c$\mssql7\data\your_data.mdf', @filename2 = N'\\yourserver\c$\mssql7\data\your_log.ldf' From ssharkins at setel.com Mon Oct 2 09:09:14 2006 From: ssharkins at setel.com (Susan Harkins) Date: Mon, 2 Oct 2006 10:09:14 -0400 Subject: [dba-SQLServer] Moving the log file In-Reply-To: Message-ID: <001601c6e62c$587b4160$97b62ad1@SUSANONE> JC, I have an article somewhere on this -- I wrote it with Mike G. If you don't get this figured out, let me know privately and I'll see if I can find an electronic copy of it. Susan H. If you are attaching the DB it's like this >From Query Analyzer RESTORE DATABASE devREDe FROM DISK = 'D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\DB.bak' WITH MOVE 'myDB_log' TO 'D:\Program Files\Microsoft SQL Server\MSSQL\DATA\DB_log.ldf' From jlawrenc1 at shaw.ca Tue Oct 3 07:37:48 2006 From: jlawrenc1 at shaw.ca (Jim Lawrence) Date: Tue, 03 Oct 2006 05:37:48 -0700 Subject: [dba-SQLServer] Saving stored procedures In-Reply-To: <001601c6e62c$587b4160$97b62ad1@SUSANONE> Message-ID: <0J6K00A3X8DCA5B0@l-daemon> Hi All: This undoubtedly will appear to be a silly problem but I do not seem to be able to get past it. It may be the late night or something. I am working in SQL 2005, in SQL Server Management Studio. I have just created a new Stored Procedure, tested it and now want to save it. It can be stored to any directory but does not save the results to the Stored Procedure list. There is something very simple that I am missing but at this late hour have no idea and the help files do not. All that is needed is for the new SP is for it to appear/stored in the list. TIA Regards Jim From paul.hartland at fsmail.net Tue Oct 3 08:37:08 2006 From: paul.hartland at fsmail.net (paul.hartland at fsmail.net) Date: Tue, 3 Oct 2006 15:37:08 +0200 (CEST) Subject: [dba-SQLServer] Saving stored procedures Message-ID: <30467276.1159882628874.JavaMail.www@wwinf3003> Jim I had the same problem when I first dabbled with this, you actually don't have to save it as far as I can remember. If you create the stored procedure, click the execute button, think this tests if all is ok...then if you refresh your stored procedure listing it should appear. Paul Message Received: Oct 03 2006, 01:37 PM From: "Jim Lawrence" To: dba-sqlserver at databaseadvisors.com Cc: Subject: [dba-SQLServer] Saving stored procedures Hi All: This undoubtedly will appear to be a silly problem but I do not seem to be able to get past it. It may be the late night or something. I am working in SQL 2005, in SQL Server Management Studio. I have just created a new Stored Procedure, tested it and now want to save it. It can be stored to any directory but does not save the results to the Stored Procedure list. There is something very simple that I am missing but at this late hour have no idea and the help files do not. All that is needed is for the new SP is for it to appear/stored in the list. TIA Regards Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com Paul Hartland paul.hartland at fsmail.net 07730 523179 From askolits at ot.com Tue Oct 3 11:13:04 2006 From: askolits at ot.com (John Skolits) Date: Tue, 3 Oct 2006 12:13:04 -0400 Subject: [dba-SQLServer] ODBC Timeouts from SQLServer? In-Reply-To: <4521AEB1.2020303@shaw.ca> Message-ID: <004a01c6e706$d14b4970$6501a8c0@LaptopXP> I have a bunch of reports that run at night (within Access MDB). The database is triggered by using command line arguments. Sometimes, I get an ODBC timeout error, but it's very inconsistent. I set all the query ODBC timeouts to 300 seconds. These routines run at about 2:30 AM to avoid heavy server loads. But, I do know, there are other backups and such running that take processor time, but my MDB queries typically run very fast. Is it possible SQLServer is timing out instead of Access and that's why the messages are happening. There are many more ways I can optimize the queries, which is the next step, but how to I find out what the SqlServer ODBC timeout value is and how do I change it? John From accessd at shaw.ca Tue Oct 3 15:32:40 2006 From: accessd at shaw.ca (Jim Lawrence) Date: Tue, 03 Oct 2006 13:32:40 -0700 Subject: [dba-SQLServer] Saving stored procedures In-Reply-To: <30467276.1159882628874.JavaMail.www@wwinf3003> Message-ID: <0J6K0032BUCQFGH2@l-daemon> Hi Paul: Thanks for the comments. The problem was occurring in my SQL 2000 and SQL 2005 versions and I was unaware of why I was getting errors on one system and was being ignored on the other system. It turns out that after a recent patch on the old system (SQL 2000) and a subsequent import/upgrade attempt (SQL 2005) things started acting weird. First only a couple of the SPs imported and when trying to add the missed SPs they refused to save completely and/or would respond with the usual innocuous MS error. I had run the checker before attempting a save and no errors.... It turned out to be a legacy coding meets the new security. (Like a shampoo salesman meets airport security.) On older SPs between each process group, within the SP a 'GO' was added. This had always worked right before. The new syntax does not need a 'GO' statement and a 'GO' statement is only required or allowed as the last statement in a SP. In SQL 2000 the app would just chop the SP at the 'GO' statement and the SQL 2005 would simply ignore what it assumes as an invalid SP. The reason for this upgrade was to stop the threats from injection-attack text compromising an otherwise valid SP. The thing that most annoyed me was that all the SPs validated perfectly and the systems either ignored the SP and did not allow it to save or responded with some unintelligible error message before scrambling the SP. This is another MS half baked fix. Thanks again for your note at least it set me on the right path and some sleep last night. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of paul.hartland at fsmail.net Sent: Tuesday, October 03, 2006 6:37 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Saving stored procedures Importance: High Jim I had the same problem when I first dabbled with this, you actually don't have to save it as far as I can remember. If you create the stored procedure, click the execute button, think this tests if all is ok...then if you refresh your stored procedure listing it should appear. Paul Message Received: Oct 03 2006, 01:37 PM From: "Jim Lawrence" To: dba-sqlserver at databaseadvisors.com Cc: Subject: [dba-SQLServer] Saving stored procedures Hi All: This undoubtedly will appear to be a silly problem but I do not seem to be able to get past it. It may be the late night or something. I am working in SQL 2005, in SQL Server Management Studio. I have just created a new Stored Procedure, tested it and now want to save it. It can be stored to any directory but does not save the results to the Stored Procedure list. There is something very simple that I am missing but at this late hour have no idea and the help files do not. All that is needed is for the new SP is for it to appear/stored in the list. TIA Regards Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com Paul Hartland paul.hartland at fsmail.net 07730 523179 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Tue Oct 3 18:28:07 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 3 Oct 2006 16:28:07 -0700 Subject: [dba-SQLServer] ODBC Timeouts from SQLServer? In-Reply-To: <004a01c6e706$d14b4970$6501a8c0@LaptopXP> References: <4521AEB1.2020303@shaw.ca> <004a01c6e706$d14b4970$6501a8c0@LaptopXP> Message-ID: One method is to run your queries in the Query Analyzer to see just how long they take, another method is to turn on the Sql Profiler to find out exactly how long they are taking, you'll need to be available for both. Many times IME it's been access that times out before sql server tho... -- Francisco On 10/3/06, John Skolits wrote: > I have a bunch of reports that run at night (within Access MDB). > The database is triggered by using command line arguments. > Sometimes, I get an ODBC timeout error, but it's very inconsistent. > I set all the query ODBC timeouts to 300 seconds. > These routines run at about 2:30 AM to avoid heavy server loads. But, I do > know, there are other backups and such running that take processor time, but > my MDB queries typically run very fast. > > Is it possible SQLServer is timing out instead of Access and that's why the > messages are happening. > > There are many more ways I can optimize the queries, which is the next step, > but how to I find out what the SqlServer ODBC timeout value is and how do I > change it? > > John > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From artful at rogers.com Tue Oct 3 18:43:01 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 3 Oct 2006 16:43:01 -0700 (PDT) Subject: [dba-SQLServer] Saving stored procedures In-Reply-To: <0J6K00A3X8DCA5B0@l-daemon> Message-ID: <20061003234301.70479.qmail@web88205.mail.re2.yahoo.com> Save = Save As, which is to a script. Assuming that your script begins "Create Procedure XXX" then just execute it, then select the Sprocs node and press F5. You should see it then. hth, Arthur ----- Original Message ---- From: Jim Lawrence To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, October 3, 2006 8:37:48 AM Subject: [dba-SQLServer] Saving stored procedures Hi All: This undoubtedly will appear to be a silly problem but I do not seem to be able to get past it. It may be the late night or something. I am working in SQL 2005, in SQL Server Management Studio. I have just created a new Stored Procedure, tested it and now want to save it. It can be stored to any directory but does not save the results to the Stored Procedure list. There is something very simple that I am missing but at this late hour have no idea and the help files do not. All that is needed is for the new SP is for it to appear/stored in the list. TIA Regards Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jlawrenc1 at shaw.ca Tue Oct 3 19:39:22 2006 From: jlawrenc1 at shaw.ca (Jim Lawrence) Date: Tue, 03 Oct 2006 17:39:22 -0700 Subject: [dba-SQLServer] Saving stored procedures In-Reply-To: <20061003234301.70479.qmail@web88205.mail.re2.yahoo.com> Message-ID: <0J6L0004V5RVNHD0@l-daemon> Hi Arthur: Thanks for that....:-) Regards Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Tuesday, October 03, 2006 4:43 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Saving stored procedures Save = Save As, which is to a script. Assuming that your script begins "Create Procedure XXX" then just execute it, then select the Sprocs node and press F5. You should see it then. hth, Arthur ----- Original Message ---- From: Jim Lawrence To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, October 3, 2006 8:37:48 AM Subject: [dba-SQLServer] Saving stored procedures Hi All: This undoubtedly will appear to be a silly problem but I do not seem to be able to get past it. It may be the late night or something. I am working in SQL 2005, in SQL Server Management Studio. I have just created a new Stored Procedure, tested it and now want to save it. It can be stored to any directory but does not save the results to the Stored Procedure list. There is something very simple that I am missing but at this late hour have no idea and the help files do not. All that is needed is for the new SP is for it to appear/stored in the list. TIA Regards Jim _______________________________________________ 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 artful at rogers.com Tue Oct 3 23:39:39 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 3 Oct 2006 21:39:39 -0700 (PDT) Subject: [dba-SQLServer] ODBC Timeouts from SQLServer? In-Reply-To: Message-ID: <20061004043939.88374.qmail@web88201.mail.re2.yahoo.com> You're right, Francisco, Access will time-out before SQL does. The immediate solution is to set the timeout to zero seconds (which equals forever). This is qualified by asserting that any given query should be exeucuted in QA first, so you can see what the time is in pure SQL. If the time is acceptable in QA, then either investigate using the Profiler or else the problem lies in the front end. ----- Original Message ---- From: Francisco Tapia To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, October 3, 2006 7:28:07 PM Subject: Re: [dba-SQLServer] ODBC Timeouts from SQLServer? One method is to run your queries in the Query Analyzer to see just how long they take, another method is to turn on the Sql Profiler to find out exactly how long they are taking, you'll need to be available for both. Many times IME it's been access that times out before sql server tho... -- Francisco On 10/3/06, John Skolits wrote: > I have a bunch of reports that run at night (within Access MDB). > The database is triggered by using command line arguments. > Sometimes, I get an ODBC timeout error, but it's very inconsistent. > I set all the query ODBC timeouts to 300 seconds. > These routines run at about 2:30 AM to avoid heavy server loads. But, I do > know, there are other backups and such running that take processor time, but > my MDB queries typically run very fast. > > Is it possible SQLServer is timing out instead of Access and that's why the > messages are happening. > > There are many more ways I can optimize the queries, which is the next step, > but how to I find out what the SqlServer ODBC timeout value is and how do I > change it? > > John > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From askolits at ot.com Wed Oct 4 12:01:58 2006 From: askolits at ot.com (John Skolits) Date: Wed, 4 Oct 2006 13:01:58 -0400 Subject: [dba-SQLServer] ODBC Timeouts from SQLServer? In-Reply-To: <20061004043939.88374.qmail@web88201.mail.re2.yahoo.com> Message-ID: <015701c6e7d6$d0e194a0$6501a8c0@LaptopXP> Thanks guys. I'll try some of your suggestions and see what happens. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, October 04, 2006 12:40 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] ODBC Timeouts from SQLServer? You're right, Francisco, Access will time-out before SQL does. The immediate solution is to set the timeout to zero seconds (which equals forever). This is qualified by asserting that any given query should be exeucuted in QA first, so you can see what the time is in pure SQL. If the time is acceptable in QA, then either investigate using the Profiler or else the problem lies in the front end. ----- Original Message ---- From: Francisco Tapia To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, October 3, 2006 7:28:07 PM Subject: Re: [dba-SQLServer] ODBC Timeouts from SQLServer? One method is to run your queries in the Query Analyzer to see just how long they take, another method is to turn on the Sql Profiler to find out exactly how long they are taking, you'll need to be available for both. Many times IME it's been access that times out before sql server tho... -- Francisco On 10/3/06, John Skolits wrote: > I have a bunch of reports that run at night (within Access MDB). > The database is triggered by using command line arguments. > Sometimes, I get an ODBC timeout error, but it's very inconsistent. > I set all the query ODBC timeouts to 300 seconds. > These routines run at about 2:30 AM to avoid heavy server loads. But, I do > know, there are other backups and such running that take processor time, but > my MDB queries typically run very fast. > > Is it possible SQLServer is timing out instead of Access and that's why the > messages are happening. > > There are many more ways I can optimize the queries, which is the next step, > but how to I find out what the SqlServer ODBC timeout value is and how do I > change it? > > John > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ 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 newsgrps at dalyn.co.nz Wed Oct 4 13:06:57 2006 From: newsgrps at dalyn.co.nz (David Emerson) Date: Thu, 05 Oct 2006 07:06:57 +1300 Subject: [dba-SQLServer] Simple Install to run SQL2000 Database Message-ID: <7.0.1.0.0.20061005065718.01ab0348@dalyn.co.nz> Group, I have a client who wants to see the progress of a development project we are writing. The database is SQL2000. He doesn't have SQL2000 on his computer. All we need is to be able to have something on his computer so that I can install a runtime of the Access XP ade and he can use it. This is only a temporary solution until he gets a server with the full SQL2000 installed on it. Since the temporary computer will not be accessible via a network, and it will not have a full version of Access XP on it, I am not sure that even if we got SQL2000 installed, we could connect to the database without coding the connection string (which is another matter). Back to my original question - Is there a free version of SQL2000 available, or will the free version of SQL2005 run SQL2000 databases. If so, does it have a tool like Enterprise manager for restoring datafiles etc? From markamatte at hotmail.com Wed Oct 4 15:16:09 2006 From: markamatte at hotmail.com (Mark A Matte) Date: Wed, 04 Oct 2006 20:16:09 +0000 Subject: [dba-SQLServer] Defrag machine with SQL 7 In-Reply-To: <449A41FC.2014.2B054F97@stuart.lexacorp.com.pg> Message-ID: Hello All, I am running SQL7 on an XP Pro machine. I tried to defrag but it tells me it cannot defrag the SQL server files. I used the 'shrink database' feature as an attempt. It did recover some space...but I still cannot defrag. Is there a way around this? Thanks, Mark A. Matte From fhtapia at gmail.com Wed Oct 4 15:44:45 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Wed, 4 Oct 2006 13:44:45 -0700 Subject: [dba-SQLServer] Defrag machine with SQL 7 In-Reply-To: References: <449A41FC.2014.2B054F97@stuart.lexacorp.com.pg> Message-ID: Sql Server Files are IN USE while Sql Server is running, in order to defrag these files stop the SQL Server instance then defrag, and resume the engine once your defrag process has completed. On 10/4/06, Mark A Matte wrote: > Hello All, > > I am running SQL7 on an XP Pro machine. I tried to defrag but it tells me > it cannot defrag the SQL server files. I used the 'shrink database' feature > as an attempt. It did recover some space...but I still cannot defrag. Is > there a way around this? > > Thanks, > > Mark A. Matte > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From stuart at lexacorp.com.pg Wed Oct 4 17:15:33 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Thu, 05 Oct 2006 08:15:33 +1000 Subject: [dba-SQLServer] Simple Install to run SQL2000 Database In-Reply-To: <7.0.1.0.0.20061005065718.01ab0348@dalyn.co.nz> References: <7.0.1.0.0.20061005065718.01ab0348@dalyn.co.nz> Message-ID: <4524BF25.14972.37FEA01@stuart.lexacorp.com.pg> Instal MSDE and the SQL Server 2000 client tools on the workstation. See http://www.microsoft.com/sql/prodinfo/previousversions/msde/prodinfo.mspx On 5 Oct 2006 at 7:06, David Emerson wrote: > Group, > > I have a client who wants to see the progress of a development > project we are writing. The database is SQL2000. He doesn't have > SQL2000 on his computer. All we need is to be able to have something > on his computer so that I can install a runtime of the Access XP ade > and he can use it. This is only a temporary solution until he gets a > server with the full SQL2000 installed on it. > > Since the temporary computer will not be accessible via a network, > and it will not have a full version of Access XP on it, I am not sure > that even if we got SQL2000 installed, we could connect to the > database without coding the connection string (which is another matter). > > Back to my original question - Is there a free version of SQL2000 > available, or will the free version of SQL2005 run SQL2000 > databases. If so, does it have a tool like Enterprise manager for > restoring datafiles etc? > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > -- Stuart From newsgrps at dalyn.co.nz Wed Oct 4 19:07:31 2006 From: newsgrps at dalyn.co.nz (David Emerson) Date: Thu, 05 Oct 2006 13:07:31 +1300 Subject: [dba-SQLServer] Simple Install to run SQL2000 Database In-Reply-To: <4524BF25.14972.37FEA01@stuart.lexacorp.com.pg> References: <7.0.1.0.0.20061005065718.01ab0348@dalyn.co.nz> <4524BF25.14972.37FEA01@stuart.lexacorp.com.pg> Message-ID: <7.0.1.0.0.20061005125654.01a50af8@dalyn.co.nz> Thanks Stuart, Does enterprise manager come with the MSDE installation or is it a separate file? I tried to find it on the Microsoft Site but couldn't work it out. David At 5/10/2006, you wrote: >Instal MSDE and the SQL Server 2000 client tools on the workstation. >See >http://www.microsoft.com/sql/prodinfo/previousversions/msde/prodinfo.mspx > > >On 5 Oct 2006 at 7:06, David Emerson wrote: > > > Group, > > > > I have a client who wants to see the progress of a development > > project we are writing. The database is SQL2000. He doesn't have > > SQL2000 on his computer. All we need is to be able to have something > > on his computer so that I can install a runtime of the Access XP ade > > and he can use it. This is only a temporary solution until he gets a > > server with the full SQL2000 installed on it. > > > > Since the temporary computer will not be accessible via a network, > > and it will not have a full version of Access XP on it, I am not sure > > that even if we got SQL2000 installed, we could connect to the > > database without coding the connection string (which is another matter). > > > > Back to my original question - Is there a free version of SQL2000 > > available, or will the free version of SQL2005 run SQL2000 > > databases. If so, does it have a tool like Enterprise manager for > > restoring datafiles etc? > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > >-- >Stuart > > >_______________________________________________ >dba-SQLServer mailing list >dba-SQLServer at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >http://www.databaseadvisors.com From stuart at lexacorp.com.pg Wed Oct 4 19:12:50 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Thu, 05 Oct 2006 10:12:50 +1000 Subject: [dba-SQLServer] Simple Install to run SQL2000 Database In-Reply-To: <7.0.1.0.0.20061005125654.01a50af8@dalyn.co.nz> References: <7.0.1.0.0.20061005065718.01ab0348@dalyn.co.nz>, <4524BF25.14972.37FEA01@stuart.lexacorp.com.pg>, <7.0.1.0.0.20061005125654.01a50af8@dalyn.co.nz> Message-ID: <4524DAA2.30569.E755765@stuart.lexacorp.com.pg> On 5 Oct 2006 at 13:07, David Emerson wrote: > Thanks Stuart, > > Does enterprise manager come with the MSDE installation or is it a > separate file? I tried to find it on the Microsoft Site but couldn't > work it out. > MSDE doesn't come with many tools :-( You'll have to instal Enterprise manager from a full SQL Server installation set onto the workstation. -- Stuart McLachlan From markamatte at hotmail.com Thu Oct 5 09:05:39 2006 From: markamatte at hotmail.com (Mark A Matte) Date: Thu, 05 Oct 2006 14:05:39 +0000 Subject: [dba-SQLServer] Defrag machine with SQL 7 In-Reply-To: Message-ID: I had tried that but no luck...then I rebooted...without starting SQL and it worked fine...guess even after I stopped SQL the files were still being called by something...or stuck in memory. Thanks, Mark A. Matte >From: "Francisco Tapia" >Reply-To: dba-sqlserver at databaseadvisors.com >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] Defrag machine with SQL 7 >Date: Wed, 4 Oct 2006 13:44:45 -0700 > >Sql Server Files are IN USE while Sql Server is running, in order to >defrag these files stop the SQL Server instance then defrag, and >resume the engine once your defrag process has completed. > >On 10/4/06, Mark A Matte wrote: > > Hello All, > > > > I am running SQL7 on an XP Pro machine. I tried to defrag but it tells >me > > it cannot defrag the SQL server files. I used the 'shrink database' >feature > > as an attempt. It did recover some space...but I still cannot defrag. >Is > > there a way around this? > > > > Thanks, > > > > Mark A. Matte > > > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > > >-- >-Francisco >http://sqlthis.blogspot.com | Tsql and More... >_______________________________________________ >dba-SQLServer mailing list >dba-SQLServer at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >http://www.databaseadvisors.com > From martyconnelly at shaw.ca Thu Oct 5 10:11:11 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Thu, 05 Oct 2006 08:11:11 -0700 Subject: [dba-SQLServer] Simple Install to run SQL2000 Database In-Reply-To: <4524DAA2.30569.E755765@stuart.lexacorp.com.pg> References: <7.0.1.0.0.20061005065718.01ab0348@dalyn.co.nz> <4524BF25.14972.37FEA01@stuart.lexacorp.com.pg> <7.0.1.0.0.20061005125654.01a50af8@dalyn.co.nz> <4524DAA2.30569.E755765@stuart.lexacorp.com.pg> Message-ID: <4525208F.9010407@shaw.ca> You could try running SQL Express 2005 in SQL 2000 degraded mode it comes with a new downloadable version of SQL Enterprise manager SQL Server Management Studio Express I have used this replacement for SQL EM 2000 comes with VB6 source code a bit sluggish running under 500 Meg http://www.asql.biz/en/ Stuart McLachlan wrote: >On 5 Oct 2006 at 13:07, David Emerson wrote: > > > >>Thanks Stuart, >> >>Does enterprise manager come with the MSDE installation or is it a >>separate file? I tried to find it on the Microsoft Site but couldn't >>work it out. >> >> >> > >MSDE doesn't come with many tools :-( > >You'll have to instal Enterprise manager from a full SQL Server installation set onto the workstation. > > -- Marty Connelly Victoria, B.C. Canada From fhtapia at gmail.com Thu Oct 5 13:34:46 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Thu, 5 Oct 2006 11:34:46 -0700 Subject: [dba-SQLServer] Defrag machine with SQL 7 In-Reply-To: References: Message-ID: when the service is stopped / sql server / sql server agent, these files are released, if they are not there may be a problem w/ the way your OS is handeling this, addtionally if you are running an A/V you may wish to not scan the mdf/ldf files so that they are released. otherwise what will happen is that it takes forever for some a/v software to release the files. On 10/5/06, Mark A Matte wrote: > I had tried that but no luck...then I rebooted...without starting SQL and it > worked fine...guess even after I stopped SQL the files were still being > called by something...or stuck in memory. > > Thanks, > > Mark A. Matte > > > >From: "Francisco Tapia" > >Reply-To: dba-sqlserver at databaseadvisors.com > >To: dba-sqlserver at databaseadvisors.com > >Subject: Re: [dba-SQLServer] Defrag machine with SQL 7 > >Date: Wed, 4 Oct 2006 13:44:45 -0700 > > > >Sql Server Files are IN USE while Sql Server is running, in order to > >defrag these files stop the SQL Server instance then defrag, and > >resume the engine once your defrag process has completed. > > > >On 10/4/06, Mark A Matte wrote: > > > Hello All, > > > > > > I am running SQL7 on an XP Pro machine. I tried to defrag but it tells > >me > > > it cannot defrag the SQL server files. I used the 'shrink database' > >feature > > > as an attempt. It did recover some space...but I still cannot defrag. > >Is > > > there a way around this? > > > > > > Thanks, > > > > > > Mark A. Matte > > > > > > > > > _______________________________________________ > > > dba-SQLServer mailing list > > > dba-SQLServer at databaseadvisors.com > > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > > http://www.databaseadvisors.com > > > > > > > > > > > >-- > >-Francisco > >http://sqlthis.blogspot.com | Tsql and More... > >_______________________________________________ > >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 > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From scapistrant at symphonyinfo.com Thu Oct 5 16:56:01 2006 From: scapistrant at symphonyinfo.com (Steve Capistrant) Date: Thu, 5 Oct 2006 16:56:01 -0500 Subject: [dba-SQLServer] Access BE to SQL References: <000001c6e888$b9282510$4b4f5a46@Symphony.local> Message-ID: <02F5B8F3D893A845A3DF342F14D80F0103A478@LAKATOS.Symphony.local> Well, looks like I'm going to be hanging out in this group a little more. My team is about to migrate an Acc/Acc (AccessFE over AccessBE) application to Acc/SQL (AccessFE to SQL Server). I'm sure this topic has been well discussed, but could I please as for some starter tips and feedback? Also, I am considering hiring out some or all of this to someone who's done it a few times, so let me know if you are interested. The Acc/Acc app is a mature 6 year old system sold commercially, but getting unwieldy in size, speed, and corruptability. Long term plan is VB.NET over SQL. Short term (1 year) is to just get the BE in place, and rewire the FE. Pushing heavy queries to the BE are expected to go a long way in improving performance, buying us time to migrate the FE later. The application has 332 tables, 940 saved queries, 239 queries dynamically defined in code, 282 reports, 119 code modules, 899 recordset manipulations, and over 25,000 lines of code. FE is 27 meg (in MDE format) and growing. Here's the essential task list as we see it (lacking experience), including an estimate of time: 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. 3. NewID modification. Adjust the programming code in all places where a new record is created and the resulting unique ID is captured. Access and SQL behave differently - Access allows capture before posting, SQL does not. 66 instances @ 15 minutes = 16.5 hours. 4. Boolean field modification. Access and SQL both support a Boolean data type SQL allows a null option whereas Access does not. All default Boolean settings in the app must be reviewed and changed as necessary to account for this difference. 664 instances @ 5 minutes = 55 hours. 5. Paging on List Views. Currently, all list views (on forms) are structured to allow display unlimited number of records (often returning hundreds of thousands of records). To minimize the traffic hit, we want to reengineer few of the biggest ones to implement paged subsets (e.g., 100 at a time). 15 major list views @ 2.5 hours each = 37.5 hours. Targeting high impact only: 5 lists@ 2.5 hours = 12.5 hours. ------- How's that look? Missing things? Over/underestimating time? Thank you in advance. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 From newsgrps at dalyn.co.nz Thu Oct 5 17:53:09 2006 From: newsgrps at dalyn.co.nz (David Emerson) Date: Fri, 06 Oct 2006 11:53:09 +1300 Subject: [dba-SQLServer] Simple Install to run SQL2000 Database In-Reply-To: <4525208F.9010407@shaw.ca> References: <7.0.1.0.0.20061005065718.01ab0348@dalyn.co.nz> <4524BF25.14972.37FEA01@stuart.lexacorp.com.pg> <7.0.1.0.0.20061005125654.01a50af8@dalyn.co.nz> <4524DAA2.30569.E755765@stuart.lexacorp.com.pg> <4525208F.9010407@shaw.ca> Message-ID: <7.0.1.0.0.20061006114212.01ae3260@dalyn.co.nz> Thanks for the help everyone. I ended up installing a full version of SQL2000. David At 6/10/2006, you wrote: >You could try running SQL Express 2005 in SQL 2000 degraded mode >it comes with a new downloadable version of SQL Enterprise manager >SQL Server Management Studio Express > >I have used this replacement for SQL EM 2000 comes with VB6 source code >a bit sluggish running under 500 Meg > >http://www.asql.biz/en/ > >Stuart McLachlan wrote: > > >On 5 Oct 2006 at 13:07, David Emerson wrote: > > > > > > > >>Thanks Stuart, > >> > >>Does enterprise manager come with the MSDE installation or is it a > >>separate file? I tried to find it on the Microsoft Site but couldn't > >>work it out. > >> > >> > >> > > > >MSDE doesn't come with many tools :-( > > > >You'll have to instal Enterprise manager from a full SQL Server > installation set onto the workstation. > > > > > >-- >Marty Connelly >Victoria, B.C. >Canada > >_______________________________________________ >dba-SQLServer mailing list >dba-SQLServer at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Thu Oct 5 20:06:31 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 5 Oct 2006 21:06:31 -0400 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <02F5B8F3D893A845A3DF342F14D80F0103A478@LAKATOS.Symphony.local> Message-ID: <004801c6e8e3$a9dcadf0$647aa8c0@m6805> Looks good. Now... As with all time estimating, a very realistic time estimate can be found by taking the number and multiplying it by 3. Then take the unit and increase it by 1. In other words, if you think it will take 15 minutes, multiply 15 times 3 (45) and up the minutes to hours. Other than that, your estimates look fine to me. Seriously though, 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours Multiply by at LEAST 3. 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. Multiply by at LEAST 3. Etc. Etc. Etc. And yes, I am serious. You will have no clue until you get in there what a mess you have. Access allows things that SQL Server does not, such as referencing home built functions in VBA inside of queries. How do you replace those? Referencing built-in VBA functions inside of queries. Easier to replace but still often not trivial. You have to learn the similarities and differences between the Access version and the SQL Server equivalent. And what about data type differences? You will end up completely rewriting portions of your application inside of SQL Server. The more "Access tricks" in the Access app, the tougher it will be to rewrite. And one thing you missed completely is testing of the changes to ensure that the result still does whatever it did originally, with exactly the same result. Access was designed from the ground up to be a RAD environment and in order to achieve this it gives you power beyond anything that SQL Server has ever imagined. I will be watching this thread closely, I can tell you that. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant Sent: Thursday, October 05, 2006 5:56 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Access BE to SQL Well, looks like I'm going to be hanging out in this group a little more. My team is about to migrate an Acc/Acc (AccessFE over AccessBE) application to Acc/SQL (AccessFE to SQL Server). I'm sure this topic has been well discussed, but could I please as for some starter tips and feedback? Also, I am considering hiring out some or all of this to someone who's done it a few times, so let me know if you are interested. The Acc/Acc app is a mature 6 year old system sold commercially, but getting unwieldy in size, speed, and corruptability. Long term plan is VB.NET over SQL. Short term (1 year) is to just get the BE in place, and rewire the FE. Pushing heavy queries to the BE are expected to go a long way in improving performance, buying us time to migrate the FE later. The application has 332 tables, 940 saved queries, 239 queries dynamically defined in code, 282 reports, 119 code modules, 899 recordset manipulations, and over 25,000 lines of code. FE is 27 meg (in MDE format) and growing. Here's the essential task list as we see it (lacking experience), including an estimate of time: 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. 3. NewID modification. Adjust the programming code in all places where a new record is created and the resulting unique ID is captured. Access and SQL behave differently - Access allows capture before posting, SQL does not. 66 instances @ 15 minutes = 16.5 hours. 4. Boolean field modification. Access and SQL both support a Boolean data type SQL allows a null option whereas Access does not. All default Boolean settings in the app must be reviewed and changed as necessary to account for this difference. 664 instances @ 5 minutes = 55 hours. 5. Paging on List Views. Currently, all list views (on forms) are structured to allow display unlimited number of records (often returning hundreds of thousands of records). To minimize the traffic hit, we want to reengineer few of the biggest ones to implement paged subsets (e.g., 100 at a time). 15 major list views @ 2.5 hours each = 37.5 hours. Targeting high impact only: 5 lists@ 2.5 hours = 12.5 hours. ------- How's that look? Missing things? Over/underestimating time? Thank you in advance. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 From scapistrant at symphonyinfo.com Thu Oct 5 21:09:13 2006 From: scapistrant at symphonyinfo.com (Steve Capistrant) Date: Thu, 5 Oct 2006 21:09:13 -0500 Subject: [dba-SQLServer] Access BE to SQL References: <000101c6e8e5$0530b1f0$4b4f5a46@Symphony.local> Message-ID: <02F5B8F3D893A845A3DF342F14D80F0103A47C@LAKATOS.Symphony.local> John, I don't know whether to smile or cry. Perhaps I'll split the difference with a sigh. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of JWColby Sent: Thu 10/5/2006 8:16 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL Looks good. Now... As with all time estimating, a very realistic time estimate can be found by taking the number and multiplying it by 3. Then take the unit and increase it by 1. In other words, if you think it will take 15 minutes, multiply 15 times 3 (45) and up the minutes to hours. Other than that, your estimates look fine to me. Seriously though, 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours Multiply by at LEAST 3. 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. Multiply by at LEAST 3. Etc. Etc. Etc. And yes, I am serious. You will have no clue until you get in there what a mess you have. Access allows things that SQL Server does not, such as referencing home built functions in VBA inside of queries. How do you replace those? Referencing built-in VBA functions inside of queries. Easier to replace but still often not trivial. You have to learn the similarities and differences between the Access version and the SQL Server equivalent. And what about data type differences? You will end up completely rewriting portions of your application inside of SQL Server. The more "Access tricks" in the Access app, the tougher it will be to rewrite. And one thing you missed completely is testing of the changes to ensure that the result still does whatever it did originally, with exactly the same result. Access was designed from the ground up to be a RAD environment and in order to achieve this it gives you power beyond anything that SQL Server has ever imagined. I will be watching this thread closely, I can tell you that. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant Sent: Thursday, October 05, 2006 5:56 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Access BE to SQL Well, looks like I'm going to be hanging out in this group a little more. My team is about to migrate an Acc/Acc (AccessFE over AccessBE) application to Acc/SQL (AccessFE to SQL Server). I'm sure this topic has been well discussed, but could I please as for some starter tips and feedback? Also, I am considering hiring out some or all of this to someone who's done it a few times, so let me know if you are interested. The Acc/Acc app is a mature 6 year old system sold commercially, but getting unwieldy in size, speed, and corruptability. Long term plan is VB.NET over SQL. Short term (1 year) is to just get the BE in place, and rewire the FE. Pushing heavy queries to the BE are expected to go a long way in improving performance, buying us time to migrate the FE later. The application has 332 tables, 940 saved queries, 239 queries dynamically defined in code, 282 reports, 119 code modules, 899 recordset manipulations, and over 25,000 lines of code. FE is 27 meg (in MDE format) and growing. Here's the essential task list as we see it (lacking experience), including an estimate of time: 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. 3. NewID modification. Adjust the programming code in all places where a new record is created and the resulting unique ID is captured. Access and SQL behave differently - Access allows capture before posting, SQL does not. 66 instances @ 15 minutes = 16.5 hours. 4. Boolean field modification. Access and SQL both support a Boolean data type SQL allows a null option whereas Access does not. All default Boolean settings in the app must be reviewed and changed as necessary to account for this difference. 664 instances @ 5 minutes = 55 hours. 5. Paging on List Views. Currently, all list views (on forms) are structured to allow display unlimited number of records (often returning hundreds of thousands of records). To minimize the traffic hit, we want to reengineer few of the biggest ones to implement paged subsets (e.g., 100 at a time). 15 major list views @ 2.5 hours each = 37.5 hours. Targeting high impact only: 5 lists@ 2.5 hours = 12.5 hours. ------- How's that look? Missing things? Over/underestimating time? Thank you in advance. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Thu Oct 5 21:40:02 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 5 Oct 2006 22:40:02 -0400 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <02F5B8F3D893A845A3DF342F14D80F0103A47C@LAKATOS.Symphony.local> Message-ID: <005101c6e8f0$ba1c4dd0$647aa8c0@m6805> LOL, you just want to be prepared. One thing I have discovered is that man tends to minimize the time required to do anything, from changing a tire to painting the house, to writing a function or query. If you are very good at whatever you are doing, you often have the experience to overcome this tendency. Professional painters just know how long painting takes, professional developers likewise. But this is not something you are familiar with and JET and SQL Server are just different animals. Thus a simple "multiply by three" might well get you in the ballpark. You will come up to speed eventually. The first half of any given set of tasks will go way slower than that, and the last half will go faster. One thing you might want to consider is moving up to SQL Server 2005. That has the full on VB.Net as the scripting language right inside of SQL Server (or so I am told). While VB.Net and VBA might not be a close match, for the kinds of things you might run into it might way better than what is available in SQL Server 2K. As an added bene, when you move the app itself to .net, you will already have the core database running on SQL Server 2005, and you will be becoming a VB.Net kinda guy. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant Sent: Thursday, October 05, 2006 10:09 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL John, I don't know whether to smile or cry. Perhaps I'll split the difference with a sigh. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of JWColby Sent: Thu 10/5/2006 8:16 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL Looks good. Now... As with all time estimating, a very realistic time estimate can be found by taking the number and multiplying it by 3. Then take the unit and increase it by 1. In other words, if you think it will take 15 minutes, multiply 15 times 3 (45) and up the minutes to hours. Other than that, your estimates look fine to me. Seriously though, 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours Multiply by at LEAST 3. 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. Multiply by at LEAST 3. Etc. Etc. Etc. And yes, I am serious. You will have no clue until you get in there what a mess you have. Access allows things that SQL Server does not, such as referencing home built functions in VBA inside of queries. How do you replace those? Referencing built-in VBA functions inside of queries. Easier to replace but still often not trivial. You have to learn the similarities and differences between the Access version and the SQL Server equivalent. And what about data type differences? You will end up completely rewriting portions of your application inside of SQL Server. The more "Access tricks" in the Access app, the tougher it will be to rewrite. And one thing you missed completely is testing of the changes to ensure that the result still does whatever it did originally, with exactly the same result. Access was designed from the ground up to be a RAD environment and in order to achieve this it gives you power beyond anything that SQL Server has ever imagined. I will be watching this thread closely, I can tell you that. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant Sent: Thursday, October 05, 2006 5:56 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Access BE to SQL Well, looks like I'm going to be hanging out in this group a little more. My team is about to migrate an Acc/Acc (AccessFE over AccessBE) application to Acc/SQL (AccessFE to SQL Server). I'm sure this topic has been well discussed, but could I please as for some starter tips and feedback? Also, I am considering hiring out some or all of this to someone who's done it a few times, so let me know if you are interested. The Acc/Acc app is a mature 6 year old system sold commercially, but getting unwieldy in size, speed, and corruptability. Long term plan is VB.NET over SQL. Short term (1 year) is to just get the BE in place, and rewire the FE. Pushing heavy queries to the BE are expected to go a long way in improving performance, buying us time to migrate the FE later. The application has 332 tables, 940 saved queries, 239 queries dynamically defined in code, 282 reports, 119 code modules, 899 recordset manipulations, and over 25,000 lines of code. FE is 27 meg (in MDE format) and growing. Here's the essential task list as we see it (lacking experience), including an estimate of time: 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. 3. NewID modification. Adjust the programming code in all places where a new record is created and the resulting unique ID is captured. Access and SQL behave differently - Access allows capture before posting, SQL does not. 66 instances @ 15 minutes = 16.5 hours. 4. Boolean field modification. Access and SQL both support a Boolean data type SQL allows a null option whereas Access does not. All default Boolean settings in the app must be reviewed and changed as necessary to account for this difference. 664 instances @ 5 minutes = 55 hours. 5. Paging on List Views. Currently, all list views (on forms) are structured to allow display unlimited number of records (often returning hundreds of thousands of records). To minimize the traffic hit, we want to reengineer few of the biggest ones to implement paged subsets (e.g., 100 at a time). 15 major list views @ 2.5 hours each = 37.5 hours. Targeting high impact only: 5 lists@ 2.5 hours = 12.5 hours. ------- How's that look? Missing things? Over/underestimating time? Thank you in advance. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From stuart at lexacorp.com.pg Thu Oct 5 22:15:01 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Fri, 06 Oct 2006 13:15:01 +1000 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <005101c6e8f0$ba1c4dd0$647aa8c0@m6805> References: <02F5B8F3D893A845A3DF342F14D80F0103A47C@LAKATOS.Symphony.local>, <005101c6e8f0$ba1c4dd0$647aa8c0@m6805> Message-ID: <452656D5.1401.14427EDB@stuart.lexacorp.com.pg> On 5 Oct 2006 at 22:40, JWColby wrote: > > One thing you might want to consider is moving up to SQL Server 2005. That > has the full on VB.Net as the scripting language right inside of SQL Server > (or so I am told). While VB.Net and VBA might not be a close match, for the > kinds of things you might run into it might way better than what is > available in SQL Server 2K. Especially since he wants to use paged sets of data. That is a real PITA in 2000, but is much easier in 2005, not least because of the new RowNumber() and Over. -- Stuart McLachlan From ssharkins at setel.com Fri Oct 6 07:43:32 2006 From: ssharkins at setel.com (Susan Harkins) Date: Fri, 6 Oct 2006 08:43:32 -0400 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <02F5B8F3D893A845A3DF342F14D80F0103A47C@LAKATOS.Symphony.local> Message-ID: <001801c6e945$0a045870$26b82ad1@SUSANONE> I'd also like to suggest an old book that Martin and I wrote together back in 2000 -- "SQL: Access to SQL Server" -- Martin wrote the half on migrating Access to SQL Server and did an excellent job. It's by Apress. If I had an author copy left, I'd just send it to you, but I don't. That book gets the best reviews and comments and everyone always compliments Martin on what a thorough job he did explaining the process. Susan H. John, I don't know whether to smile or cry. Perhaps I'll split the difference with a sigh. From rl_stewart at highstream.net Fri Oct 6 08:48:28 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Fri, 06 Oct 2006 08:48:28 -0500 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: References: Message-ID: <6.2.3.4.2.20061006084557.023e9c48@pop3.highstream.net> VB.Net is not built in to SQL Server. The ability to us external languages as assemblies (compiled code) is built in. You still have to use VS 2005 to built the functions or whatever and then SQL Server can use them. But, SQL Server/T-SQL can also be used to create functions natively. At 09:40 PM 10/5/2006, you wrote: >Date: Thu, 5 Oct 2006 22:40:02 -0400 >From: "JWColby" >Subject: Re: [dba-SQLServer] Access BE to SQL >To: >Message-ID: <005101c6e8f0$ba1c4dd0$647aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >LOL, you just want to be prepared. > >One thing I have discovered is that man tends to minimize the time required >to do anything, from changing a tire to painting the house, to writing a >function or query. If you are very good at whatever you are doing, you >often have the experience to overcome this tendency. Professional painters >just know how long painting takes, professional developers likewise. But >this is not something you are familiar with and JET and SQL Server are just >different animals. Thus a simple "multiply by three" might well get you in >the ballpark. You will come up to speed eventually. The first half of any >given set of tasks will go way slower than that, and the last half will go >faster. > >One thing you might want to consider is moving up to SQL Server 2005. That >has the full on VB.Net as the scripting language right inside of SQL Server >(or so I am told). While VB.Net and VBA might not be a close match, for the >kinds of things you might run into it might way better than what is >available in SQL Server 2K. As an added bene, when you move the app itself >to .net, you will already have the core database running on SQL Server 2005, >and you will be becoming a VB.Net kinda guy. > >John W. Colby From rl_stewart at highstream.net Fri Oct 6 08:43:46 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Fri, 06 Oct 2006 08:43:46 -0500 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: References: Message-ID: <6.2.3.4.2.20061006084019.024f1168@pop3.highstream.net> Actually John, you can reference home made functions in SQL Server, they just have to be created in SQL Server and not Access. I use them all the time. Yes, he has some light areas and number 1 is one of them. There is a lot more naming that you should do in SQL Server that you do in Access, indexes, foreign key relationships, constraints, etc. And redesigning the application to use stored procedures, after creating all of the stored procedures, is going to take a while. At 09:40 PM 10/5/2006, you wrote: >Date: Thu, 5 Oct 2006 21:06:31 -0400 >From: "JWColby" >Subject: Re: [dba-SQLServer] Access BE to SQL >To: >Message-ID: <004801c6e8e3$a9dcadf0$647aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >Looks good. Now... > >As with all time estimating, a very realistic time estimate can be found by >taking the number and multiplying it by 3. Then take the unit and increase >it by 1. In other words, if you think it will take 15 minutes, multiply 15 >times 3 (45) and up the minutes to hours. > >Other than that, your estimates look fine to me. > >Seriously though, > >1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, >some indexes. 332 instances @ 10 minutes = 55 hours > >Multiply by at LEAST 3. > >2. Convert queries to views. Convert high-impact queries into Views and >Stored Procedures. For each of those migrated queries, redesign filtering >code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = >362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = >75 hours. > >Multiply by at LEAST 3. > >Etc. > >Etc. > >Etc. > >And yes, I am serious. You will have no clue until you get in there what a >mess you have. Access allows things that SQL Server does not, such as >referencing home built functions in VBA inside of queries. How do you >replace those? Referencing built-in VBA functions inside of queries. >Easier to replace but still often not trivial. You have to learn the >similarities and differences between the Access version and the SQL Server >equivalent. And what about data type differences? > >You will end up completely rewriting portions of your application inside of >SQL Server. The more "Access tricks" in the Access app, the tougher it will >be to rewrite. > >And one thing you missed completely is testing of the changes to ensure that >the result still does whatever it did originally, with exactly the same >result. > >Access was designed from the ground up to be a RAD environment and in order >to achieve this it gives you power beyond anything that SQL Server has ever >imagined. > >I will be watching this thread closely, I can tell you that. > >John W. Colby From jwcolby at colbyconsulting.com Fri Oct 6 09:00:32 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Fri, 6 Oct 2006 10:00:32 -0400 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <6.2.3.4.2.20061006084019.024f1168@pop3.highstream.net> Message-ID: <005801c6e94f$cb0cf4f0$647aa8c0@m6805> Robert, Yes, but SQL Server does not have VBA, which is my point. It has a language of sorts but it is simply not equivalent. Thus there is no way to just take your vba functions and "use them" in SQL Server. You have to translate each one that is used in any sql statement, one by one, testing that the results are equivalent. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Friday, October 06, 2006 9:44 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL Actually John, you can reference home made functions in SQL Server, they just have to be created in SQL Server and not Access. I use them all the time. Yes, he has some light areas and number 1 is one of them. There is a lot more naming that you should do in SQL Server that you do in Access, indexes, foreign key relationships, constraints, etc. And redesigning the application to use stored procedures, after creating all of the stored procedures, is going to take a while. At 09:40 PM 10/5/2006, you wrote: >Date: Thu, 5 Oct 2006 21:06:31 -0400 >From: "JWColby" >Subject: Re: [dba-SQLServer] Access BE to SQL >To: >Message-ID: <004801c6e8e3$a9dcadf0$647aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >Looks good. Now... > >As with all time estimating, a very realistic time estimate can be >found by taking the number and multiplying it by 3. Then take the unit >and increase it by 1. In other words, if you think it will take 15 >minutes, multiply 15 times 3 (45) and up the minutes to hours. > >Other than that, your estimates look fine to me. > >Seriously though, > >1. Migrate Data to SQL. Resetting of autonumbers, referential >integrity, some indexes. 332 instances @ 10 minutes = 55 hours > >Multiply by at LEAST 3. > >2. Convert queries to views. Convert high-impact queries into Views and >Stored Procedures. For each of those migrated queries, redesign >filtering code to pass parameters back to SQL Server. 1451 instances @ >15 minutes = >362.75 hours. Limiting to high impact queries: 300 instances @ 15 >minutes = >75 hours. > >Multiply by at LEAST 3. > >Etc. > >Etc. > >Etc. > >And yes, I am serious. You will have no clue until you get in there >what a mess you have. Access allows things that SQL Server does not, >such as referencing home built functions in VBA inside of queries. How >do you replace those? Referencing built-in VBA functions inside of queries. >Easier to replace but still often not trivial. You have to learn the >similarities and differences between the Access version and the SQL >Server equivalent. And what about data type differences? > >You will end up completely rewriting portions of your application >inside of SQL Server. The more "Access tricks" in the Access app, the >tougher it will be to rewrite. > >And one thing you missed completely is testing of the changes to ensure >that the result still does whatever it did originally, with exactly the >same result. > >Access was designed from the ground up to be a RAD environment and in >order to achieve this it gives you power beyond anything that SQL >Server has ever imagined. > >I will be watching this thread closely, I can tell you that. > >John W. Colby _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Fri Oct 6 09:05:41 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Fri, 6 Oct 2006 10:05:41 -0400 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <6.2.3.4.2.20061006084557.023e9c48@pop3.highstream.net> Message-ID: <005901c6e950$830adae0$647aa8c0@m6805> For those interested, a google: Yes but TSql has a specific job to do and generic programming is not it. http://www.developer.com/net/net/article.php/3528601 http://www.devx.com/dotnet/Article/21286 John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Friday, October 06, 2006 9:48 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL VB.Net is not built in to SQL Server. The ability to us external languages as assemblies (compiled code) is built in. You still have to use VS 2005 to built the functions or whatever and then SQL Server can use them. But, SQL Server/T-SQL can also be used to create functions natively. At 09:40 PM 10/5/2006, you wrote: >Date: Thu, 5 Oct 2006 22:40:02 -0400 >From: "JWColby" >Subject: Re: [dba-SQLServer] Access BE to SQL >To: >Message-ID: <005101c6e8f0$ba1c4dd0$647aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >LOL, you just want to be prepared. > >One thing I have discovered is that man tends to minimize the time >required to do anything, from changing a tire to painting the house, to >writing a function or query. If you are very good at whatever you are >doing, you often have the experience to overcome this tendency. >Professional painters just know how long painting takes, professional >developers likewise. But this is not something you are familiar with >and JET and SQL Server are just different animals. Thus a simple >"multiply by three" might well get you in the ballpark. You will come >up to speed eventually. The first half of any given set of tasks will >go way slower than that, and the last half will go faster. > >One thing you might want to consider is moving up to SQL Server 2005. >That has the full on VB.Net as the scripting language right inside of >SQL Server (or so I am told). While VB.Net and VBA might not be a >close match, for the kinds of things you might run into it might way >better than what is available in SQL Server 2K. As an added bene, when >you move the app itself to .net, you will already have the core >database running on SQL Server 2005, and you will be becoming a VB.Net kinda guy. > >John W. Colby _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From DavidL at sierranevada.com Fri Oct 6 09:55:52 2006 From: DavidL at sierranevada.com (David Lewis) Date: Fri, 6 Oct 2006 07:55:52 -0700 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: Message-ID: <00101736F13D774F88C54058CB2663C8BCFE34@celebration.sierranevada.corp> Steve: I agree with John. You have a decent start on the estimating, but in my experience (I've done similar sized projects) each of those taskes will 1) take far longer to implement, and more importantly 2) take a very substantial block of time to plan. I found that the preparation and planning took far more time than the implementation, actually. For example, designing indexes and performance tuning queries and sp's is no quick matter. It sounds as if the access app sort of grew organically. If this is the case, you have a good opportunity to give it some structure, but that is a very large job. If you approach the project as a series of pieces that need to be made to run on an sql server platform, the project may go quicker but you will be left with a maintenance nightmare -- too much of the code and logic and design philosophy will reside in the head(s) of one or a few developers. Good job security for them, bad for the company. Another thing to give consideration to is how you will keep data in sync. You will begin the transition to sql server, and in that time of several weeks presumably the access app will still run. The initial upload of all the data is a chore in itself, and it will be duplicated again when you have to bring in the final few weeks or so of data. The sequence of these imports will be important if you have referential integrity turned on. If not, and you allow identity inserts (assuming you are using autonumber id's), there are almost guaranteed to be clean-up issues. Well, it brings back memories... Enjoy the ride. D. Lewis ------------------------------ Message: 2 Date: Thu, 5 Oct 2006 16:56:01 -0500 From: "Steve Capistrant" Subject: [dba-SQLServer] Access BE to SQL To: Message-ID: <02F5B8F3D893A845A3DF342F14D80F0103A478 at LAKATOS.Symphony.local> Content-Type: text/plain; charset="iso-8859-1" Well, looks like I'm going to be hanging out in this group a little more. My team is about to migrate an Acc/Acc (AccessFE over AccessBE) application to Acc/SQL (AccessFE to SQL Server). I'm sure this topic has been well discussed, but could I please as for some starter tips and feedback? Also, I am considering hiring out some or all of this to someone who's done it a few times, so let me know if you are interested. The Acc/Acc app is a mature 6 year old system sold commercially, but getting unwieldy in size, speed, and corruptability. Long term plan is VB.NET over SQL. Short term (1 year) is to just get the BE in place, and rewire the FE. Pushing heavy queries to the BE are expected to go a long way in improving performance, buying us time to migrate the FE later. The application has 332 tables, 940 saved queries, 239 queries dynamically defined in code, 282 reports, 119 code modules, 899 recordset manipulations, and over 25,000 lines of code. FE is 27 meg (in MDE format) and growing. Here's the essential task list as we see it (lacking experience), including an estimate of time: 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. 3. NewID modification. Adjust the programming code in all places where a new record is created and the resulting unique ID is captured. Access and SQL behave differently - Access allows capture before posting, SQL does not. 66 instances @ 15 minutes = 16.5 hours. 4. Boolean field modification. Access and SQL both support a Boolean data type SQL allows a null option whereas Access does not. All default Boolean settings in the app must be reviewed and changed as necessary to account for this difference. 664 instances @ 5 minutes = 55 hours. 5. Paging on List Views. Currently, all list views (on forms) are structured to allow display unlimited number of records (often returning hundreds of thousands of records). To minimize the traffic hit, we want to reengineer few of the biggest ones to implement paged subsets (e.g., 100 at a time). 15 major list views @ 2.5 hours each = 37.5 hours. Targeting high impact only: 5 lists@ 2.5 hours = 12.5 hours. ------- How's that look? Missing things? Over/underestimating time? Thank you in advance. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 From jwcolby at colbyconsulting.com Fri Oct 6 10:59:21 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Fri, 6 Oct 2006 11:59:21 -0400 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <00101736F13D774F88C54058CB2663C8BCFE34@celebration.sierranevada.corp> Message-ID: <005d01c6e960$63f7bc30$647aa8c0@m6805> David, Steve, I did something "similar" when I normalized an access database. I had to be able to allow the client to continue entering data, and yet at some point "switch over" What I did was build up a set of queries that did the data migration, and placed them in macros - one of the damned few times I ever used macros. This allowed me to build the queries, get the sequences required for the migration figured out and working (parent first, then child, grandchild etc. When the whole MIGRATION thing was working I was able to push a button and run all of the macros that ran all of the queries, in exactly the correct order to migrate the entire database, top to bottom. Once THAT was working, I could go building forms and stuff to display the new data structure, enter new data, reports etc. When I was ready and tested, I just ran the macro and the client (who had been training the users in the new system) just switched one day to the new system. It really did work that way, just one day they turned off the old and turned on the new. It was a PITA to do of course but realistically you need the real (new) data to work with to ensure that the new forms / reports etc work, so it was worth the effort. Plus no issues of "did we enter that data in the old system?". John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David Lewis Sent: Friday, October 06, 2006 10:56 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL Steve: I agree with John. You have a decent start on the estimating, but in my experience (I've done similar sized projects) each of those taskes will 1) take far longer to implement, and more importantly 2) take a very substantial block of time to plan. I found that the preparation and planning took far more time than the implementation, actually. For example, designing indexes and performance tuning queries and sp's is no quick matter. It sounds as if the access app sort of grew organically. If this is the case, you have a good opportunity to give it some structure, but that is a very large job. If you approach the project as a series of pieces that need to be made to run on an sql server platform, the project may go quicker but you will be left with a maintenance nightmare -- too much of the code and logic and design philosophy will reside in the head(s) of one or a few developers. Good job security for them, bad for the company. Another thing to give consideration to is how you will keep data in sync. You will begin the transition to sql server, and in that time of several weeks presumably the access app will still run. The initial upload of all the data is a chore in itself, and it will be duplicated again when you have to bring in the final few weeks or so of data. The sequence of these imports will be important if you have referential integrity turned on. If not, and you allow identity inserts (assuming you are using autonumber id's), there are almost guaranteed to be clean-up issues. Well, it brings back memories... Enjoy the ride. D. Lewis ------------------------------ Message: 2 Date: Thu, 5 Oct 2006 16:56:01 -0500 From: "Steve Capistrant" Subject: [dba-SQLServer] Access BE to SQL To: Message-ID: <02F5B8F3D893A845A3DF342F14D80F0103A478 at LAKATOS.Symphony.local> Content-Type: text/plain; charset="iso-8859-1" Well, looks like I'm going to be hanging out in this group a little more. My team is about to migrate an Acc/Acc (AccessFE over AccessBE) application to Acc/SQL (AccessFE to SQL Server). I'm sure this topic has been well discussed, but could I please as for some starter tips and feedback? Also, I am considering hiring out some or all of this to someone who's done it a few times, so let me know if you are interested. The Acc/Acc app is a mature 6 year old system sold commercially, but getting unwieldy in size, speed, and corruptability. Long term plan is VB.NET over SQL. Short term (1 year) is to just get the BE in place, and rewire the FE. Pushing heavy queries to the BE are expected to go a long way in improving performance, buying us time to migrate the FE later. The application has 332 tables, 940 saved queries, 239 queries dynamically defined in code, 282 reports, 119 code modules, 899 recordset manipulations, and over 25,000 lines of code. FE is 27 meg (in MDE format) and growing. Here's the essential task list as we see it (lacking experience), including an estimate of time: 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, some indexes. 332 instances @ 10 minutes = 55 hours 2. Convert queries to views. Convert high-impact queries into Views and Stored Procedures. For each of those migrated queries, redesign filtering code to pass parameters back to SQL Server. 1451 instances @ 15 minutes = 362.75 hours. Limiting to high impact queries: 300 instances @ 15 minutes = 75 hours. 3. NewID modification. Adjust the programming code in all places where a new record is created and the resulting unique ID is captured. Access and SQL behave differently - Access allows capture before posting, SQL does not. 66 instances @ 15 minutes = 16.5 hours. 4. Boolean field modification. Access and SQL both support a Boolean data type SQL allows a null option whereas Access does not. All default Boolean settings in the app must be reviewed and changed as necessary to account for this difference. 664 instances @ 5 minutes = 55 hours. 5. Paging on List Views. Currently, all list views (on forms) are structured to allow display unlimited number of records (often returning hundreds of thousands of records). To minimize the traffic hit, we want to reengineer few of the biggest ones to implement paged subsets (e.g., 100 at a time). 15 major list views @ 2.5 hours each = 37.5 hours. Targeting high impact only: 5 lists@ 2.5 hours = 12.5 hours. ------- How's that look? Missing things? Over/underestimating time? Thank you in advance. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From rl_stewart at highstream.net Fri Oct 6 11:31:11 2006 From: rl_stewart at highstream.net (Robert L. Stewart) Date: Fri, 06 Oct 2006 11:31:11 -0500 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: References: Message-ID: <6.2.3.4.2.20061006113028.0248e2f0@pop3.highstream.net> As you do with any migration between languages/systems. At 10:59 AM 10/6/2006, you wrote: >Date: Fri, 6 Oct 2006 10:00:32 -0400 >From: "JWColby" >Subject: Re: [dba-SQLServer] Access BE to SQL >To: >Message-ID: <005801c6e94f$cb0cf4f0$647aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >Robert, > >Yes, but SQL Server does not have VBA, which is my point. It has a language >of sorts but it is simply not equivalent. Thus there is no way to just take >your vba functions and "use them" in SQL Server. You have to translate each >one that is used in any sql statement, one by one, testing that the results >are equivalent. > > >John W. Colby From ldoering at symphonyinfo.com Fri Oct 6 11:58:57 2006 From: ldoering at symphonyinfo.com (Liz Doering) Date: Fri, 6 Oct 2006 11:58:57 -0500 Subject: [dba-SQLServer] Access BE to SQL References: <000801c6e945$55670d30$4b4f5a46@Symphony.local> Message-ID: <02F5B8F3D893A845A3DF342F14D80F0106696A@LAKATOS.Symphony.local> Susan, Thanks for the confirmation. I insisted Steve and I needed your book when this project was first discussed--a couple of years ago. We've moved offices since then, but I know he hasn't gotten rid of it! Liz Doering Senior Developer Symphony Information Services www.symphonyinfo.com 763-391-7400 x802 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Susan Harkins Sent: Fri 10/6/2006 7:45 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL I'd also like to suggest an old book that Martin and I wrote together back in 2000 -- "SQL: Access to SQL Server" -- Martin wrote the half on migrating Access to SQL Server and did an excellent job. It's by Apress. If I had an author copy left, I'd just send it to you, but I don't. That book gets the best reviews and comments and everyone always compliments Martin on what a thorough job he did explaining the process. Susan H. John, I don't know whether to smile or cry. Perhaps I'll split the difference with a sigh. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From ssharkins at setel.com Fri Oct 6 12:35:32 2006 From: ssharkins at setel.com (Susan Harkins) Date: Fri, 6 Oct 2006 13:35:32 -0400 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <02F5B8F3D893A845A3DF342F14D80F0106696A@LAKATOS.Symphony.local> Message-ID: <002201c6e96d$d4b92b90$a232fad1@SUSANONE> OOOOOOOOOO! ;) Always glad to help! ;) I don't know if Martin's on this list, but I know he's the king of upsizing... Just in case he's listening. :) Susan H. Susan, Thanks for the confirmation. I insisted Steve and I needed your book when this project was first discussed--a couple of years ago. We've moved offices since then, but I know he hasn't gotten rid of it! From mwp.reid at qub.ac.uk Fri Oct 6 12:37:55 2006 From: mwp.reid at qub.ac.uk (Martin Reid) Date: Fri, 6 Oct 2006 18:37:55 +0100 Subject: [dba-SQLServer] Access BE to SQL References: <002201c6e96d$d4b92b90$a232fad1@SUSANONE> Message-ID: (<: Always listening. Thanks for the kinds words. Anything I can do to help just shout. If you are working in SQL Server 2005 I have been looking at the migration assistant. Its available for download but is not a finished product. I have the new version which is also incomplete but begins to deal with queries etc It still has some very useful features and worth a look. There is always Upsizing Pro whcih can be used BEFORE you do anything to produce reports on possible problems in your database - this is useful for SQL Server 2000 and 2005 but mostly 2000. The biggest thing I have learnt is to plan everything before you actually do anything at all re the database particulary a big application. JC summed it up very well. Again if I can help just shout. Best Wishes Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Susan Harkins Sent: Fri 06/10/2006 18:35 To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL OOOOOOOOOO! ;) Always glad to help! ;) I don't know if Martin's on this list, but I know he's the king of upsizing... Just in case he's listening. :) Susan H. Susan, Thanks for the confirmation. I insisted Steve and I needed your book when this project was first discussed--a couple of years ago. We've moved offices since then, but I know he hasn't gotten rid of it! _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From martyconnelly at shaw.ca Fri Oct 6 12:50:11 2006 From: martyconnelly at shaw.ca (MartyConnelly) Date: Fri, 06 Oct 2006 10:50:11 -0700 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <02F5B8F3D893A845A3DF342F14D80F0106696A@LAKATOS.Symphony.local> References: <000801c6e945$55670d30$4b4f5a46@Symphony.local> <02F5B8F3D893A845A3DF342F14D80F0106696A@LAKATOS.Symphony.local> Message-ID: <45269753.2050608@shaw.ca> You might want to pick up a copy of speed ferret, with that number of tables you have to make sure that the field names in Access conform to SQL field naming conventions. For example if you have a space in a field name you might want to change to an underscore. Speed ferret will change all occurrences in forms reports etc. Liz Doering wrote: >Susan, > >Thanks for the confirmation. I insisted Steve and I needed your book when this project was first discussed--a couple of years ago. We've moved offices since then, but I know he hasn't gotten rid of it! > >Liz Doering >Senior Developer >Symphony Information Services >www.symphonyinfo.com >763-391-7400 x802 > >________________________________ > >From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Susan Harkins >Sent: Fri 10/6/2006 7:45 AM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] Access BE to SQL > > > >I'd also like to suggest an old book that Martin and I wrote together back >in 2000 -- "SQL: Access to SQL Server" -- Martin wrote the half on migrating >Access to SQL Server and did an excellent job. It's by Apress. If I had an >author copy left, I'd just send it to you, but I don't. > >That book gets the best reviews and comments and everyone always compliments >Martin on what a thorough job he did explaining the process. > >Susan H. > >John, I don't know whether to smile or cry. Perhaps I'll split the >difference with a sigh. > > >_______________________________________________ >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 > > > >------------------------------------------------------------------------ > >No virus found in this incoming message. >Checked by AVG Free Edition. >Version: 7.1.407 / Virus Database: 268.13.0/465 - Release Date: 06/10/2006 > > -- Marty Connelly Victoria, B.C. Canada From scapistrant at symphonyinfo.com Fri Oct 6 13:28:06 2006 From: scapistrant at symphonyinfo.com (Steve Capistrant) Date: Fri, 6 Oct 2006 13:28:06 -0500 Subject: [dba-SQLServer] Access BE to SQL References: <02F5B8F3D893A845A3DF342F14D80F0103A47C@LAKATOS.Symphony.local>, <005101c6e8f0$ba1c4dd0$647aa8c0@m6805> <000401c6e8f7$cad63580$4b4f5a46@Symphony.local> Message-ID: <02F5B8F3D893A845A3DF342F14D80F0103A480@LAKATOS.Symphony.local> Thanks, that is a really useful observation. I thought that the logic for generating paged data sets where handled mostly at the front end, and didn't realize that BE tools (can) have these functions built in. Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com www.symphonyinfo.com Main: 763-391-7400 ext 801 Toll Free: 888-357-1373 ext 801 Direct: 612-237-0075 ________________________________ From: dba-sqlserver-bounces at databaseadvisors.com on behalf of Stuart McLachlan Sent: Thu 10/5/2006 10:30 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL On 5 Oct 2006 at 22:40, JWColby wrote: > > One thing you might want to consider is moving up to SQL Server 2005. That > has the full on VB.Net as the scripting language right inside of SQL Server > (or so I am told). While VB.Net and VBA might not be a close match, for the > kinds of things you might run into it might way better than what is > available in SQL Server 2K. Especially since he wants to use paged sets of data. That is a real PITA in 2000, but is much easier in 2005, not least because of the new RowNumber() and Over. -- Stuart McLachlan _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From tuxedoman888 at gmail.com Fri Oct 6 14:41:54 2006 From: tuxedoman888 at gmail.com (Billy Pang) Date: Fri, 6 Oct 2006 12:41:54 -0700 Subject: [dba-SQLServer] Access BE to SQL In-Reply-To: <02F5B8F3D893A845A3DF342F14D80F0103A478@LAKATOS.Symphony.local> References: <000001c6e888$b9282510$4b4f5a46@Symphony.local> <02F5B8F3D893A845A3DF342F14D80F0103A478@LAKATOS.Symphony.local> Message-ID: <7c8826480610061241k778696e5l8bafd92429fbb039@mail.gmail.com> not sure what you mean by resetting autonumbers but during the data migration you can use identity_insert setting to the values from autonumber field in access to an identity field in sql server. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_set-set_7zas.asp also, if you find that it saves time, you might want to consider turning off all foreign keys in the target db, import the data and then (crossing your fingers) turn on the foreign key constraints using WITH CHECK (go look up WITH CHECK and WITH NOCHECK for the alter constraint statement in books on line http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_set-set_7zas.asp ); hope that helps Billy Pang http://dbnotes.blogspot.com/ "Once the game is over, the King and the pawn go back in the same box." - Italian proverb On 10/5/06, Steve Capistrant wrote: > > > 1. Migrate Data to SQL. Resetting of autonumbers, referential integrity, > some indexes. 332 instances @ 10 minutes = 55 hours > > > -- > From fhtapia at gmail.com Mon Oct 9 18:34:28 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Mon, 9 Oct 2006 16:34:28 -0700 Subject: [dba-SQLServer] Sql DBA/Dev needed Message-ID: Hello group, I realize that most people on the list are either employed, or self-employed, but I am in need of finding a MS SQL Server DBA/ Developer in the SoCal Area. They should have strong troubleshooting skills and be proficient in TSQL. Have at least 2+yrs of Sql Server 2000 experience and a great work ethic. Email me if you are interested in an pursuing this job lead. Thanks, -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From jwcolby at colbyconsulting.com Thu Oct 12 12:14:20 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Thu, 12 Oct 2006 13:14:20 -0400 Subject: [dba-SQLServer] The log file for TempDB is full In-Reply-To: <7c8826480610061241k778696e5l8bafd92429fbb039@mail.gmail.com> Message-ID: <011c01c6ee21$dc529950$647aa8c0@m6805> I am getting a notice that the log file is full (and in fact the disk is out of space). The warning says to backup the transaction log for the database to free up some space. When I go in to EM and try to backup the TempDB, the transaction log is not selectable (is grayed out) and if I try to backup the Tempdb itself I get a message that I can't backup the TempDB. What gives and how do I get out? I have a nice raid 5 terabyte data partition and a 400gb log partition, but I initially set up SQL Server to place all of its stuff out on the D drive, which is only about 250g and is not RAID. Sigh. What do I do to back up this file so that I can continue? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Billy Pang Sent: Friday, October 06, 2006 3:42 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Access BE to SQL not sure what you mean by resetting autonumbers but during the data migration you can use identity_insert setting to the values from autonumber field in access to an identity field in sql server. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ set-set_7zas.asp also, if you find that it saves time, you might want to consider turning off all foreign keys in the target db, import the data and then (crossing your fingers) turn on the foreign key constraints using WITH CHECK (go look up WITH CHECK and WITH NOCHECK for the alter constraint statement in books on line http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ set-set_7zas.asp ); hope that helps Billy Pang http://dbnotes.blogspot.com/ "Once the game is over, the King and the pawn go back in the same box." - Italian proverb On 10/5/06, Steve Capistrant wrote: > > > 1. Migrate Data to SQL. Resetting of autonumbers, referential > integrity, some indexes. 332 instances @ 10 minutes = 55 hours > > > -- > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Thu Oct 12 15:57:27 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Thu, 12 Oct 2006 13:57:27 -0700 Subject: [dba-SQLServer] The log file for TempDB is full In-Reply-To: <011c01c6ee21$dc529950$647aa8c0@m6805> References: <7c8826480610061241k778696e5l8bafd92429fbb039@mail.gmail.com> <011c01c6ee21$dc529950$647aa8c0@m6805> Message-ID: John, Your problem is destailed here: http://sqlserver2000.databases.aspfaq.com/why-is-tempdb-full-and-how-can-i-prevent-this-from-happening.html you will find some good workarounds...let me know if you are not able to use any of them. -- Francisco On 10/12/06, JWColby wrote: > I am getting a notice that the log file is full (and in fact the disk is out > of space). The warning says to backup the transaction log for the database > to free up some space. When I go in to EM and try to backup the TempDB, the > transaction log is not selectable (is grayed out) and if I try to backup the > Tempdb itself I get a message that I can't backup the TempDB. > > What gives and how do I get out? > > I have a nice raid 5 terabyte data partition and a 400gb log partition, but > I initially set up SQL Server to place all of its stuff out on the D drive, > which is only about 250g and is not RAID. Sigh. > > What do I do to back up this file so that I can continue? > > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Billy Pang > Sent: Friday, October 06, 2006 3:42 PM > To: dba-sqlserver at databaseadvisors.com > Subject: Re: [dba-SQLServer] Access BE to SQL > > not sure what you mean by resetting autonumbers but during the data > migration you can use identity_insert setting to the values from autonumber > field in access to an identity field in sql server. > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ > set-set_7zas.asp > > also, if you find that it saves time, you might want to consider turning off > all foreign keys in the target db, import the data and then (crossing your > fingers) turn on the foreign key constraints using WITH CHECK (go look up > WITH CHECK and WITH NOCHECK for the alter constraint statement in books on > line > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ > set-set_7zas.asp > ); > > hope that helps > > Billy Pang > http://dbnotes.blogspot.com/ > "Once the game is over, the King and the pawn go back in the same box." - > Italian proverb > > > On 10/5/06, Steve Capistrant wrote: > > > > > > 1. Migrate Data to SQL. Resetting of autonumbers, referential > > integrity, some indexes. 332 instances @ 10 minutes = 55 hours > > > > > > -- > > > _______________________________________________ > 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 > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Thu Oct 12 16:13:51 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Thu, 12 Oct 2006 14:13:51 -0700 Subject: [dba-SQLServer] The log file for TempDB is full In-Reply-To: References: <7c8826480610061241k778696e5l8bafd92429fbb039@mail.gmail.com> <011c01c6ee21$dc529950$647aa8c0@m6805> Message-ID: to move your TempDB use the following --- use master go Alter database tempdb modify file (name = tempdev, filename = 'Drive:\Path\tempdb.mdf') go Alter database tempdb modify file (name = templog, filename = 'Drive:\Path\templog.ldf') Go --- There is more info here as well: http://www.databasejournal.com/features/mssql/article.php/3379901 On 10/12/06, Francisco Tapia wrote: > John, > Your problem is destailed here: > http://sqlserver2000.databases.aspfaq.com/why-is-tempdb-full-and-how-can-i-prevent-this-from-happening.html > you will find some good workarounds...let me know if you are not able > to use any of them. > > -- > Francisco > > > On 10/12/06, JWColby wrote: > > I am getting a notice that the log file is full (and in fact the disk is out > > of space). The warning says to backup the transaction log for the database > > to free up some space. When I go in to EM and try to backup the TempDB, the > > transaction log is not selectable (is grayed out) and if I try to backup the > > Tempdb itself I get a message that I can't backup the TempDB. > > > > What gives and how do I get out? > > > > I have a nice raid 5 terabyte data partition and a 400gb log partition, but > > I initially set up SQL Server to place all of its stuff out on the D drive, > > which is only about 250g and is not RAID. Sigh. > > > > What do I do to back up this file so that I can continue? > > > > > > John W. Colby > > Colby Consulting > > www.ColbyConsulting.com > > > > -----Original Message----- > > From: dba-sqlserver-bounces at databaseadvisors.com > > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Billy Pang > > Sent: Friday, October 06, 2006 3:42 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: Re: [dba-SQLServer] Access BE to SQL > > > > not sure what you mean by resetting autonumbers but during the data > > migration you can use identity_insert setting to the values from autonumber > > field in access to an identity field in sql server. > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ > > set-set_7zas.asp > > > > also, if you find that it saves time, you might want to consider turning off > > all foreign keys in the target db, import the data and then (crossing your > > fingers) turn on the foreign key constraints using WITH CHECK (go look up > > WITH CHECK and WITH NOCHECK for the alter constraint statement in books on > > line > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ > > set-set_7zas.asp > > ); > > > > hope that helps > > > > Billy Pang > > http://dbnotes.blogspot.com/ > > "Once the game is over, the King and the pawn go back in the same box." - > > Italian proverb > > > > > > On 10/5/06, Steve Capistrant wrote: > > > > > > > > > 1. Migrate Data to SQL. Resetting of autonumbers, referential > > > integrity, some indexes. 332 instances @ 10 minutes = 55 hours > > > > > > > > > -- > > > > > _______________________________________________ > > 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 > > > > > > > -- > -Francisco > http://sqlthis.blogspot.com | Tsql and More... > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From jwcolby at colbyconsulting.com Mon Oct 16 14:27:06 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 16 Oct 2006 15:27:06 -0400 Subject: [dba-SQLServer] The log file for TempDB is full In-Reply-To: Message-ID: <001301c6f159$122c6300$657aa8c0@m6805> That worked. Thanks Francisco. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Thursday, October 12, 2006 5:14 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] The log file for TempDB is full to move your TempDB use the following --- use master go Alter database tempdb modify file (name = tempdev, filename = 'Drive:\Path\tempdb.mdf') go Alter database tempdb modify file (name = templog, filename = 'Drive:\Path\templog.ldf') Go --- There is more info here as well: http://www.databasejournal.com/features/mssql/article.php/3379901 On 10/12/06, Francisco Tapia wrote: From paul.hartland at fsmail.net Wed Oct 18 06:51:46 2006 From: paul.hartland at fsmail.net (paul.hartland at fsmail.net) Date: Wed, 18 Oct 2006 13:51:46 +0200 (CEST) Subject: [dba-SQLServer] Updating DateTime Field IN SQL Server With Just The Time Message-ID: <10468859.1161172306777.JavaMail.www@wwinf3003> To all, I have a little problem which I am sure this group can tell me the answer to....I have a datetime field in SQL Server 2000 I have an insert stored procedure which I pass the time to to put into the table, however it always puts the date in front of the time....I can input the time directly and no date gets put in front, I can also use a recordset with an update which works (but is slower)....Is there anyway I can insert a time into a datetime field in SQL Server 2000 without it putting the date in front using a stored procedure. Thanks in advance for any help on this as it's driving me nuts. Paul Hartland paul.hartland at fsmail.net 07730 523179 From artful at rogers.com Wed Oct 18 10:37:55 2006 From: artful at rogers.com (artful at rogers.com) Date: Wed, 18 Oct 2006 08:37:55 -0700 (PDT) Subject: [dba-SQLServer] Reporting Services Installation failed In-Reply-To: <10468859.1161172306777.JavaMail.www@wwinf3003> Message-ID: <20061018153755.18487.qmail@web88210.mail.re2.yahoo.com> A while back, I had to remove a bunch of software, including SQL 2005. Then when I tried to re-install it, the components dialog had Reporting Services greyed out. I did various things (completely un-install, check the IIS settings in Windows setup, etc.), and something that I did finally enabled the RS checkbox. I thought I was off to the races, but I thought too soon. Late in the installation, I got the following error: Setup failed to read IISWebSite table. I checked the installation log and found the following lines: ConfigureIIs: Error 0x8009000f: failed to get metabase data ConfigureIIs: Error 0x8009000f: Failed to get key from metabase while searching for web servers ConfigureIIs: Error 0x8009000f: Failed to find web root ConfigureIIs: Error 0x8009000f: failed to read IIsWebSite table MSI (s) (D4!40) [10:24:56:265] : Product: Microsoft SQL Server 2005 Reporting Services -- Error 25602. The setup failed to read IIsWebSite table. The error code is -2146893809. Error 25602. The setup failed to read IIsWebSite table. The error code is -2146893809. I have no idea how to correct this problem. Can anyone help? TIA, Arthur From jwcolby at colbyconsulting.com Wed Oct 18 10:50:35 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 18 Oct 2006 11:50:35 -0400 Subject: [dba-SQLServer] Reporting Services Installation failed In-Reply-To: <20061018153755.18487.qmail@web88210.mail.re2.yahoo.com> Message-ID: <002a01c6f2cd$27bb94a0$657aa8c0@m6805> I use PC Tools Registry Mechanic to cleanup EVERYTHING after installs and de-installs. And every once in a while just for grins. It really works. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Wednesday, October 18, 2006 11:38 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Reporting Services Installation failed A while back, I had to remove a bunch of software, including SQL 2005. Then when I tried to re-install it, the components dialog had Reporting Services greyed out. I did various things (completely un-install, check the IIS settings in Windows setup, etc.), and something that I did finally enabled the RS checkbox. I thought I was off to the races, but I thought too soon. Late in the installation, I got the following error: Setup failed to read IISWebSite table. I checked the installation log and found the following lines: ConfigureIIs: Error 0x8009000f: failed to get metabase data ConfigureIIs: Error 0x8009000f: Failed to get key from metabase while searching for web servers ConfigureIIs: Error 0x8009000f: Failed to find web root ConfigureIIs: Error 0x8009000f: failed to read IIsWebSite table MSI (s) (D4!40) [10:24:56:265] : Product: Microsoft SQL Server 2005 Reporting Services -- Error 25602. The setup failed to read IIsWebSite table. The error code is -2146893809. Error 25602. The setup failed to read IIsWebSite table. The error code is -2146893809. I have no idea how to correct this problem. Can anyone help? TIA, Arthur _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Thu Oct 19 13:24:08 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Thu, 19 Oct 2006 11:24:08 -0700 Subject: [dba-SQLServer] Reporting Services Installation failed In-Reply-To: <002a01c6f2cd$27bb94a0$657aa8c0@m6805> References: <20061018153755.18487.qmail@web88210.mail.re2.yahoo.com> <002a01c6f2cd$27bb94a0$657aa8c0@m6805> Message-ID: I've also tried ccleaner wich is free but I noticed that Registry Mechanic is free for some time now.. http://slickdeals.net/?nojs=1 Get the free license here: http://slickdeals.net/?pno=8250&lno=2&afsrc=1 download the software here: http://slickdeals.net/?pno=8250&lno=3&afsrc=1 On 10/18/06, JWColby wrote: > I use PC Tools Registry Mechanic to cleanup EVERYTHING after installs and > de-installs. And every once in a while just for grins. It really works. > > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > -----Original Message----- > From: dba-sqlserver-bounces at databaseadvisors.com > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of > artful at rogers.com > Sent: Wednesday, October 18, 2006 11:38 AM > To: dba-sqlserver at databaseadvisors.com > Subject: [dba-SQLServer] Reporting Services Installation failed > > A while back, I had to remove a bunch of software, including SQL 2005. Then > when I tried to re-install it, the components dialog had Reporting Services > greyed out. I did various things (completely un-install, check the IIS > settings in Windows setup, etc.), and something that I did finally enabled > the RS checkbox. I thought I was off to the races, but I thought too soon. > Late in the installation, I got the following error: > > Setup failed to read IISWebSite table. I checked the installation log and > found the following lines: > > ConfigureIIs: Error 0x8009000f: failed to get metabase data > ConfigureIIs: Error 0x8009000f: Failed to get key from metabase while > searching for web servers > ConfigureIIs: Error 0x8009000f: Failed to find web root > ConfigureIIs: Error 0x8009000f: failed to read IIsWebSite table MSI (s) > (D4!40) [10:24:56:265] : Product: Microsoft SQL Server 2005 Reporting > Services -- Error 25602. The setup failed to read IIsWebSite table. The > error code is -2146893809. > > Error 25602. The setup failed to read IIsWebSite table. The error code is > -2146893809. > > I have no idea how to correct this problem. Can anyone help? > > TIA, > Arthur > > > _______________________________________________ > 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 > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From fhtapia at gmail.com Fri Oct 20 10:38:15 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Fri, 20 Oct 2006 08:38:15 -0700 Subject: [dba-SQLServer] Bulk Insert Errors in DTS Message-ID: I have the following txt file and designated bcp format to allow me to do a bulk insert typically bulk inserts are for large files but this file gives me the same error. Maybe someone here can show me what I am doing wrong. (Thanks in advance) The Error that I am getting is "Error Source: Microsoft OLE DB Provider for SQL Server Error Description: Bulk insert data conversion derror (type mismatch) for row1, column 2 (CHECK_DATA) ---Table---- CREATE TABLE [tbl_File_Log] ( [SEQ] [varchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL , [CHECK_DATA] [float] NULL , [SQL_COL] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL , [AV_FLD] [int] NULL , [TOT_REC_CNT] [numeric](18, 0) NULL ) ON [PRIMARY] -------------- ----IMPORT FILE DATA---- SEQ CHECK_DATA SQL_COL AV_FLD TOT_REC_COUNT 1 574 ------ ---FromatFile------------ 7.0 5 1 SQLCHAR 0 50 "\t" 1 SEQ 2 SQLCHAR 0 8 "\t" 2 CHECK_DATA 3 SQLCHAR 0 50 "\t" 3 SQL_COL 4 SQLCHAR 0 4 "\t" 4 AV_FLD 5 SQLCHAR 0 19 "\r\n" 5 TOT_REC_CNT ------------------------------ -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From stuart at lexacorp.com.pg Fri Oct 20 17:36:06 2006 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Sat, 21 Oct 2006 08:36:06 +1000 Subject: [dba-SQLServer] Bulk Insert Errors in DTS In-Reply-To: References: Message-ID: <45394F56.1151.7587314@stuart.lexacorp.com.pg> On 20 Oct 2006 at 8:38, Francisco Tapia wrote: > Error Description: Bulk insert data conversion derror (type mismatch) > for row1, column 2 (CHECK_DATA) It's failing on the first row, second column > ---Table---- > CREATE TABLE [tbl_File_Log] ( > [SEQ] [varchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL , > [CHECK_DATA] [float] NULL , which it expects to be a float. > ----IMPORT FILE DATA---- > SEQ CHECK_DATA SQL_COL AV_FLD TOT_REC_COUNT The first row is a header so the second column in character data not numeric You need to either delete the header row, or specify that that data has a header row. -- Stuart From markamatte at hotmail.com Mon Oct 23 15:37:01 2006 From: markamatte at hotmail.com (Mark A Matte) Date: Mon, 23 Oct 2006 20:37:01 +0000 Subject: [dba-SQLServer] SP works sometimes In-Reply-To: <45394F56.1151.7587314@stuart.lexacorp.com.pg> Message-ID: Hello All, I have SQL7 and I use query analyzer to loop through set of results...these results are actually the criteria part of an SQL statement. This query calls a SP. My SP is below. It works...then next time I try to run, I have to edit and tweek and finally I end up exactly with the same SP I started with...and now it runs. This does not make any sense to me. can anyone shed some light? Thanks, Mark A. Matte P.S...The errors are below...but I know it works...because I ran it yesterday...but had to tweek and edit...but end up with same exact SP but it runs????? CREATE PROCEDURE [Select_Records_1] @ID nvarchar(255) AS declare @sql as varchar(1000) declare @nsql as nchar(3000) set @sql='insert into tblHaier_ID(case_id,Criteria) SELECT case_id, "'+ at ID+'" as Criteria FROM tblCase where creation_date>"07/01/2006" and '+ at id set @nsql=@sql set nocount on exec sp_executesql @nsql set nocount off ********************* ERRORS Server: Msg 103, Level 15, State 7, Line 1949556518 The identifier that starts with '(rc_descrlong Like '%haier%' or rc_descrlong Like '%higher%' or rc_descrlong Like '%haer%' or rc_descrlong Like '%hire%' or rc_d' is too long. Maximum length is 128. Server: Msg 103, Level 15, State 7, Line 1 The identifier that starts with '(sr_other_brand Like '%haier%' or sr_other_brand Like '%higher%' or sr_other_brand Like '%haer%' or sr_other_brand Like '%hire%'' is too long. Maximum length is 128. Server: Msg 103, Level 15, State 7, Line 1 The identifier that starts with '(sr_other_reason Like '%haier%' or sr_other_reason Like '%higher%' or sr_other_reason Like '%haer%' or sr_other_reason Like '%hi' is too long. Maximum length is 128. Server: Msg 207, Level 16, State 3, Line 1 Invalid column name '(sr_other_prod Like '%harr%' or sr_other_prod Like '%42ep24%')'. Server: Msg 207, Level 16, State 1, Line 1 Invalid column name '07/01/2006'. Server: Msg 103, Level 15, State 7, Line 1 The identifier that starts with '(model Like '%haier%' or model Like '%higher%' or model Like '%haer%' or model Like '%hire%' or model Like '%hair%' or model Lik' is too long. Maximum length is 128. Server: Msg 103, Level 15, State 7, Line 1 The identifier that starts with '(rc_summary Like '%haier%' or rc_summary Like '%higher%' or rc_summary Like '%haer%' or rc_summary Like '%hire%' or rc_summary L' is too long. Maximum length is 128. Server: Msg 103, Level 15, State 7, Line 1 The identifier that starts with '(sr_other_prod Like '%haier%' or sr_other_prod Like '%higher%' or sr_other_prod Like '%haer%' or sr_other_prod Like '%hire%' or ' is too long. Maximum length is 128. Server: Msg 207, Level 16, State 3, Line 1 Invalid column name '(sr_other_brand Like '%harr%' or sr_other_brand Like '%42ep24%')'. Server: Msg 207, Level 16, State 1, Line 1 Invalid column name '07/01/2006'. Server: Msg 207, Level 16, State 3, Line 1 Invalid column name '(sr_other_reason Like '%harr%' or sr_other_reason Like '%42ep24%')'. Server: Msg 207, Level 16, State 1, Line 1 Invalid column name '07/01/2006'. _________________________________________________________________ Try Search Survival Kits: Fix up your home and better handle your cash with Live Search! http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=hmtagline From mikedorism at verizon.net Mon Oct 23 17:21:39 2006 From: mikedorism at verizon.net (Doris Manning) Date: Mon, 23 Oct 2006 18:21:39 -0400 Subject: [dba-SQLServer] SP works sometimes In-Reply-To: Message-ID: <001a01c6f6f1$9ca8d7a0$2f01a8c0@Kermit> Your problems lie in your mixing of single quotes (') and double quotes ("). You don't use double quotes (") in T-SQL statements. Dates in SQL are surrounded in single quotes ('). I've also found it helpful to preface all strings with the N designator to be sure they are interpreted properly. Doris Manning From artful at rogers.com Mon Oct 23 18:51:00 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 23 Oct 2006 16:51:00 -0700 (PDT) Subject: [dba-SQLServer] SP works sometimes In-Reply-To: <001a01c6f6f1$9ca8d7a0$2f01a8c0@Kermit> Message-ID: <20061023235100.70932.qmail@web88207.mail.re2.yahoo.com> Quite right, Doris. But I think there is something else missing. The last part makes no sense, I think: where creation_date>"07/01/2006" and '+ at id This makes no sense. It could have been a simple typo slip-up, but if not then how is this going to parse into anything sensible? The AND is going to make any such statement incomprehensible. A larger question: Why bother dynamically creating a SQL statement to do this thing, when you could quite easily create a variant of this sproc that drops the params into the statement, rather than constructing the statement and executing it? Perhaps I'm having a senior moment, but I can't fathom the need to do it this way. You don't have to build a statement just because you're doing a nested SELECT. Or perhaps I'm missing something. It wouldn't be the first time. Arthur CREATE PROCEDURE [Select_Records_1] ( @ID nvarchar(255) ) AS INSERT INTO tblHaier_ID (case_id, Criteria) SELECT Case_id declare @sql as varchar(1000) declare @nsql as nchar(3000) set @sql='insert into tblHaier_ID(case_id,Criteria) SELECT case_id, "'+ at ID+'" as Criteria FROM tblCase where creation_date>"07/01/2006" and '+ at id set @nsql=@sql set nocount on exec sp_executesql @nsql set nocount off ----- Original Message ---- From: Doris Manning To: dba-sqlserver at databaseadvisors.com Sent: Monday, October 23, 2006 6:21:39 PM Subject: Re: [dba-SQLServer] SP works sometimes Your problems lie in your mixing of single quotes (') and double quotes ("). You don't use double quotes (") in T-SQL statements. Dates in SQL are surrounded in single quotes ('). I've also found it helpful to preface all strings with the N designator to be sure they are interpreted properly. Doris Manning _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From markamatte at hotmail.com Mon Oct 23 21:41:57 2006 From: markamatte at hotmail.com (Mark A Matte) Date: Tue, 24 Oct 2006 02:41:57 +0000 Subject: [dba-SQLServer] SP works sometimes In-Reply-To: <20061023235100.70932.qmail@web88207.mail.re2.yahoo.com> Message-ID: Thank both of you very much for your feedback. I'll start with what I'm trying to do. I have the need to query up 6 fields for different variations of different words using wild cards...sometimes upto 40 different sql statements...so my use of >"'+ at ID+'" as Criteria is necesarry to have singe and double quotes...because @ID is actually the criteria that was used to isolate the record...since the text is actually the criteria part of my SQL...I have to surround it with double quotes. Now for the creation_date>"07/01/2006" and '+ at id part of things...as I said my @ID is actually the end of my criteria. below is an example of what is passed: @ID=(rc_descrlong Like '%haier%' or rc_descrlong Like '%higher%' or rc_descrlong Like '%haer%' or rc_descrlong Like '%hire%' or rc_descrlong Like '%hair%' or rc_descrlong Like '%hare%' or rc_descrlong Like '%harr%' or rc_descrlong Like '%42ep24%') So...I have upto 40 statements like this one with different words and different fields. I use this SP so I can run all 40 SQL statements in a row without having to sit and push the buttton 40 times. If there is a better way please share...SQL I know...SQL Server I am very new to. Thanks, Mark A. Matte >From: >Reply-To: dba-sqlserver at databaseadvisors.com >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] SP works sometimes >Date: Mon, 23 Oct 2006 16:51:00 -0700 (PDT) > >Quite right, Doris. But I think there is something else missing. The last >part makes no sense, I think: > >where creation_date>"07/01/2006" and '+ at id > >This makes no sense. It could have been a simple typo slip-up, but if not >then how is this going to parse into anything sensible? The AND is going to >make any such statement incomprehensible. > >A larger question: Why bother dynamically creating a SQL statement to do >this thing, when you could quite easily create a variant of this sproc that >drops the params into the statement, rather than constructing the statement >and executing it? Perhaps I'm having a senior moment, but I can't fathom >the need to do it this way. You don't have to build a statement just >because you're doing a nested SELECT. > >Or perhaps I'm missing something. It wouldn't be the first time. > >Arthur > >CREATE PROCEDURE [Select_Records_1] >( @ID nvarchar(255) >) >AS >INSERT INTO tblHaier_ID >(case_id, Criteria) >SELECT Case_id >declare @sql as varchar(1000) >declare @nsql as nchar(3000) >set @sql='insert into tblHaier_ID(case_id,Criteria) SELECT case_id, >"'+ at ID+'" as Criteria FROM tblCase where creation_date>"07/01/2006" and >'+ at id >set @nsql=@sql >set nocount on >exec sp_executesql @nsql >set nocount off > > >----- Original Message ---- >From: Doris Manning >To: dba-sqlserver at databaseadvisors.com >Sent: Monday, October 23, 2006 6:21:39 PM >Subject: Re: [dba-SQLServer] SP works sometimes > >Your problems lie in your mixing of single quotes (') and double quotes >("). >You don't use double quotes (") in T-SQL statements. Dates in SQL are >surrounded in single quotes ('). > >I've also found it helpful to preface all strings with the N designator to >be sure they are interpreted properly. > >Doris Manning > > >_______________________________________________ >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 > _________________________________________________________________ All-in-one security and maintenance for your PC. Get a free 90-day trial! http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail From artful at rogers.com Tue Oct 24 15:50:53 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 24 Oct 2006 13:50:53 -0700 (PDT) Subject: [dba-SQLServer] SP works sometimes In-Reply-To: Message-ID: <20061024205053.72903.qmail@web88209.mail.re2.yahoo.com> Thanks for the illumination. Now I understand the problem a little better. As I read your example I was becoming convinced that regex might be a better approach, but the last one doesn't fit the pattern. However, if your example really does illustrate the typical similarity of your search targets then regex is worth a look. Arthur ----- Original Message ---- From: Mark A Matte To: dba-sqlserver at databaseadvisors.com Sent: Monday, October 23, 2006 10:41:57 PM Subject: Re: [dba-SQLServer] SP works sometimes Thank both of you very much for your feedback. I'll start with what I'm trying to do. I have the need to query up 6 fields for different variations of different words using wild cards...sometimes upto 40 different sql statements...so my use of >"'+ at ID+'" as Criteria is necesarry to have singe and double quotes...because @ID is actually the criteria that was used to isolate the record...since the text is actually the criteria part of my SQL...I have to surround it with double quotes. Now for the creation_date>"07/01/2006" and '+ at id part of things...as I said my @ID is actually the end of my criteria. below is an example of what is passed: @ID=(rc_descrlong Like '%haier%' or rc_descrlong Like '%higher%' or rc_descrlong Like '%haer%' or rc_descrlong Like '%hire%' or rc_descrlong Like '%hair%' or rc_descrlong Like '%hare%' or rc_descrlong Like '%harr%' or rc_descrlong Like '%42ep24%') So...I have upto 40 statements like this one with different words and different fields. I use this SP so I can run all 40 SQL statements in a row without having to sit and push the buttton 40 times. If there is a better way please share...SQL I know...SQL Server I am very new to. Thanks, Mark A. Matte >From: >Reply-To: dba-sqlserver at databaseadvisors.com >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] SP works sometimes >Date: Mon, 23 Oct 2006 16:51:00 -0700 (PDT) > >Quite right, Doris. But I think there is something else missing. The last >part makes no sense, I think: > >where creation_date>"07/01/2006" and '+ at id > >This makes no sense. It could have been a simple typo slip-up, but if not >then how is this going to parse into anything sensible? The AND is going to >make any such statement incomprehensible. > >A larger question: Why bother dynamically creating a SQL statement to do >this thing, when you could quite easily create a variant of this sproc that >drops the params into the statement, rather than constructing the statement >and executing it? Perhaps I'm having a senior moment, but I can't fathom >the need to do it this way. You don't have to build a statement just >because you're doing a nested SELECT. > >Or perhaps I'm missing something. It wouldn't be the first time. > >Arthur > >CREATE PROCEDURE [Select_Records_1] >( @ID nvarchar(255) >) >AS >INSERT INTO tblHaier_ID >(case_id, Criteria) >SELECT Case_id >declare @sql as varchar(1000) >declare @nsql as nchar(3000) >set @sql='insert into tblHaier_ID(case_id,Criteria) SELECT case_id, >"'+ at ID+'" as Criteria FROM tblCase where creation_date>"07/01/2006" and >'+ at id >set @nsql=@sql >set nocount on >exec sp_executesql @nsql >set nocount off > > >----- Original Message ---- >From: Doris Manning >To: dba-sqlserver at databaseadvisors.com >Sent: Monday, October 23, 2006 6:21:39 PM >Subject: Re: [dba-SQLServer] SP works sometimes > >Your problems lie in your mixing of single quotes (') and double quotes >("). >You don't use double quotes (") in T-SQL statements. Dates in SQL are >surrounded in single quotes ('). > >I've also found it helpful to preface all strings with the N designator to >be sure they are interpreted properly. > >Doris Manning > > >_______________________________________________ >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 > _________________________________________________________________ All-in-one security and maintenance for your PC. Get a free 90-day trial! http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From markamatte at hotmail.com Tue Oct 24 16:14:43 2006 From: markamatte at hotmail.com (Mark A Matte) Date: Tue, 24 Oct 2006 21:14:43 +0000 Subject: [dba-SQLServer] SP works sometimes In-Reply-To: <20061024205053.72903.qmail@web88209.mail.re2.yahoo.com> Message-ID: Arthur, Thanks again, but I just sent the first example I had...I had not heard of 'regex' and your statement " really confused me...but after researching it I realised the logic behing the suggestion. In the example I gave I was trying to find reference to a company named 'HAIER' pronounced (hire or hare)...and those were the variations I came up with...the last was a model number...so if the record made any reference to the company or model I wanted it. Below is a better example or what I use. Thanks again, Mark A. Matte @ID=((rc_descrlong Like '% ks%' or rc_descrlong Like '%kans%') And rc_descrlong Like '%water%' And rc_descrlong Like '%heater%') >From: >Reply-To: dba-sqlserver at databaseadvisors.com >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] SP works sometimes >Date: Tue, 24 Oct 2006 13:50:53 -0700 (PDT) > >Thanks for the illumination. Now I understand the problem a little better. >As I read your example I was becoming convinced that regex might be a >better approach, but the last one doesn't fit the pattern. However, if your >example really does illustrate the typical similarity of your search >targets then regex is worth a look. > >Arthur > >----- Original Message ---- >From: Mark A Matte >To: dba-sqlserver at databaseadvisors.com >Sent: Monday, October 23, 2006 10:41:57 PM >Subject: Re: [dba-SQLServer] SP works sometimes > >Thank both of you very much for your feedback. I'll start with what I'm >trying to do. I have the need to query up 6 fields for different >variations >of different words using wild cards...sometimes upto 40 different sql >statements...so my use of >"'+ at ID+'" as Criteria is necesarry to have singe >and double quotes...because @ID is actually the criteria that was used to >isolate the record...since the text is actually the criteria part of my >SQL...I have to surround it with double quotes. > >Now for the creation_date>"07/01/2006" and '+ at id part of things...as I said >my @ID is actually the end of my criteria. below is an example of what is >passed: > >@ID=(rc_descrlong Like '%haier%' or rc_descrlong Like '%higher%' or >rc_descrlong Like '%haer%' or rc_descrlong Like '%hire%' or rc_descrlong >Like '%hair%' or rc_descrlong Like '%hare%' or rc_descrlong Like '%harr%' >or >rc_descrlong Like '%42ep24%') > >So...I have upto 40 statements like this one with different words and >different fields. I use this SP so I can run all 40 SQL statements in a >row >without having to sit and push the buttton 40 times. > >If there is a better way please share...SQL I know...SQL Server I am very >new to. > >Thanks, > >Mark A. Matte > > > >From: > >Reply-To: dba-sqlserver at databaseadvisors.com > >To: dba-sqlserver at databaseadvisors.com > >Subject: Re: [dba-SQLServer] SP works sometimes > >Date: Mon, 23 Oct 2006 16:51:00 -0700 (PDT) > > > >Quite right, Doris. But I think there is something else missing. The last > >part makes no sense, I think: > > > >where creation_date>"07/01/2006" and '+ at id > > > >This makes no sense. It could have been a simple typo slip-up, but if not > >then how is this going to parse into anything sensible? The AND is going >to > >make any such statement incomprehensible. > > > >A larger question: Why bother dynamically creating a SQL statement to do > >this thing, when you could quite easily create a variant of this sproc >that > >drops the params into the statement, rather than constructing the >statement > >and executing it? Perhaps I'm having a senior moment, but I can't fathom > >the need to do it this way. You don't have to build a statement just > >because you're doing a nested SELECT. > > > >Or perhaps I'm missing something. It wouldn't be the first time. > > > >Arthur > > > >CREATE PROCEDURE [Select_Records_1] > >( @ID nvarchar(255) > >) > >AS > >INSERT INTO tblHaier_ID > >(case_id, Criteria) > >SELECT Case_id > >declare @sql as varchar(1000) > >declare @nsql as nchar(3000) > >set @sql='insert into tblHaier_ID(case_id,Criteria) SELECT case_id, > >"'+ at ID+'" as Criteria FROM tblCase where creation_date>"07/01/2006" and > >'+ at id > >set @nsql=@sql > >set nocount on > >exec sp_executesql @nsql > >set nocount off > > > > > >----- Original Message ---- > >From: Doris Manning > >To: dba-sqlserver at databaseadvisors.com > >Sent: Monday, October 23, 2006 6:21:39 PM > >Subject: Re: [dba-SQLServer] SP works sometimes > > > >Your problems lie in your mixing of single quotes (') and double quotes > >("). > >You don't use double quotes (") in T-SQL statements. Dates in SQL are > >surrounded in single quotes ('). > > > >I've also found it helpful to preface all strings with the N designator >to > >be sure they are interpreted properly. > > > >Doris Manning > > > > > >_______________________________________________ > >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 > > > >_________________________________________________________________ >All-in-one security and maintenance for your PC. Get a free 90-day trial! >http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail > >_______________________________________________ >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 > _________________________________________________________________ Find a local pizza place, music store, museum and more?then map the best route! http://local.live.com?FORM=MGA001 From artful at rogers.com Tue Oct 24 16:55:20 2006 From: artful at rogers.com (artful at rogers.com) Date: Tue, 24 Oct 2006 14:55:20 -0700 (PDT) Subject: [dba-SQLServer] Weird Problem with SQL 2005 Message-ID: <20061024215520.27516.qmail@web88207.mail.re2.yahoo.com> I had to do a system restore on my box recently. HP makes this nice, since it stores the initial footprint on a read-only partitition. After reinstalling Windows, I then reinstalled SQL 2005 and Visual Studio 2005. When installing SQL 2005, however, the Reporting Services checkbox was greyed out. It wasn't that way before. Anyone got any idea why I can't install RS? I've poked around and I can't see anything amiss. TIA, Arthur From dmcafee at pacbell.net Tue Oct 24 17:29:16 2006 From: dmcafee at pacbell.net (David Mcafee) Date: Tue, 24 Oct 2006 15:29:16 -0700 (PDT) Subject: [dba-SQLServer] SP works sometimes In-Reply-To: <20061024205053.72903.qmail@web88209.mail.re2.yahoo.com> Message-ID: <20061024222916.54334.qmail@web80813.mail.mud.yahoo.com> Don't you mean SOUNDEX ? ----- Original Message ---- From: artful at rogers.com To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, October 24, 2006 1:50:53 PM Subject: Re: [dba-SQLServer] SP works sometimes Thanks for the illumination. Now I understand the problem a little better. As I read your example I was becoming convinced that regex might be a better approach, but the last one doesn't fit the pattern. However, if your example really does illustrate the typical similarity of your search targets then regex is worth a look. Arthur ----- Original Message ---- From: Mark A Matte To: dba-sqlserver at databaseadvisors.com Sent: Monday, October 23, 2006 10:41:57 PM Subject: Re: [dba-SQLServer] SP works sometimes Thank both of you very much for your feedback. I'll start with what I'm trying to do. I have the need to query up 6 fields for different variations of different words using wild cards...sometimes upto 40 different sql statements...so my use of >"'+ at ID+'" as Criteria is necesarry to have singe and double quotes...because @ID is actually the criteria that was used to isolate the record...since the text is actually the criteria part of my SQL...I have to surround it with double quotes. Now for the creation_date>"07/01/2006" and '+ at id part of things...as I said my @ID is actually the end of my criteria. below is an example of what is passed: @ID=(rc_descrlong Like '%haier%' or rc_descrlong Like '%higher%' or rc_descrlong Like '%haer%' or rc_descrlong Like '%hire%' or rc_descrlong Like '%hair%' or rc_descrlong Like '%hare%' or rc_descrlong Like '%harr%' or rc_descrlong Like '%42ep24%') So...I have upto 40 statements like this one with different words and different fields. I use this SP so I can run all 40 SQL statements in a row without having to sit and push the buttton 40 times. If there is a better way please share...SQL I know...SQL Server I am very new to. Thanks, Mark A. Matte >From: >Reply-To: dba-sqlserver at databaseadvisors.com >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] SP works sometimes >Date: Mon, 23 Oct 2006 16:51:00 -0700 (PDT) > >Quite right, Doris. But I think there is something else missing. The last >part makes no sense, I think: > >where creation_date>"07/01/2006" and '+ at id > >This makes no sense. It could have been a simple typo slip-up, but if not >then how is this going to parse into anything sensible? The AND is going to >make any such statement incomprehensible. > >A larger question: Why bother dynamically creating a SQL statement to do >this thing, when you could quite easily create a variant of this sproc that >drops the params into the statement, rather than constructing the statement >and executing it? Perhaps I'm having a senior moment, but I can't fathom >the need to do it this way. You don't have to build a statement just >because you're doing a nested SELECT. > >Or perhaps I'm missing something. It wouldn't be the first time. > >Arthur > >CREATE PROCEDURE [Select_Records_1] >( @ID nvarchar(255) >) >AS >INSERT INTO tblHaier_ID >(case_id, Criteria) >SELECT Case_id >declare @sql as varchar(1000) >declare @nsql as nchar(3000) >set @sql='insert into tblHaier_ID(case_id,Criteria) SELECT case_id, >"'+ at ID+'" as Criteria FROM tblCase where creation_date>"07/01/2006" and >'+ at id >set @nsql=@sql >set nocount on >exec sp_executesql @nsql >set nocount off > > >----- Original Message ---- >From: Doris Manning >To: dba-sqlserver at databaseadvisors.com >Sent: Monday, October 23, 2006 6:21:39 PM >Subject: Re: [dba-SQLServer] SP works sometimes > >Your problems lie in your mixing of single quotes (') and double quotes >("). >You don't use double quotes (") in T-SQL statements. Dates in SQL are >surrounded in single quotes ('). > >I've also found it helpful to preface all strings with the N designator to >be sure they are interpreted properly. > >Doris Manning > > >_______________________________________________ >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 > _________________________________________________________________ All-in-one security and maintenance for your PC. Get a free 90-day trial! http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail _______________________________________________ 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 paul.hartland at fsmail.net Wed Oct 25 04:54:41 2006 From: paul.hartland at fsmail.net (paul.hartland at fsmail.net) Date: Wed, 25 Oct 2006 11:54:41 +0200 (CEST) Subject: [dba-SQLServer] OT - Infragistics Ultragrid on Visual Basic 6.0 Form Message-ID: <28867723.1161770081337.JavaMail.www@wwinf3204.me-wanadoo.net> To all, I have cross posted this as I don't know if that many of you out there would have used or still be using the Infragistics suite (mainly the UltraGrid). I have a grid with one of the columns set to a dropdown on the fly, and I create and populate the valuelist for it on the fly. This all works fine, I got to the employees record, click onto their training tab and it displays exactly what I want......BUT the problem is if I make a selection from the dropdown, it just nulls the training id all the time....All the help files I can find seems though I am doing this correctly but I must be missing something. If anyone out there thinks they may be able to help me, feel free to contact me on here or offline, as I have now been working on this for 3.25 hours and it is really starting to get to me :( Thanks in advance for all your help. Paul Hartland Paul Hartland paul.hartland at fsmail.net 07730 523179 From artful at rogers.com Wed Oct 25 10:16:04 2006 From: artful at rogers.com (artful at rogers.com) Date: Wed, 25 Oct 2006 08:16:04 -0700 (PDT) Subject: [dba-SQLServer] SP works sometimes Message-ID: <20061025151605.13931.qmail@web88205.mail.re2.yahoo.com> No, I meant regex. ----- Original Message ---- From: David Mcafee To: dba-sqlserver at databaseadvisors.com Sent: Tuesday, October 24, 2006 6:29:16 PM Subject: Re: [dba-SQLServer] SP works sometimes Don't you mean SOUNDEX ? From cfoust at infostatsystems.com Wed Oct 25 14:43:09 2006 From: cfoust at infostatsystems.com (Charlotte Foust) Date: Wed, 25 Oct 2006 12:43:09 -0700 Subject: [dba-SQLServer] [AccessD] OT - Infragistics Ultragrid on Visual Basic 6.0 Form In-Reply-To: <28867723.1161770081337.JavaMail.www@wwinf3204.me-wanadoo.net> Message-ID: Wish I could help, but I'm only familiar with the .Net implementations of the Infragistics grids. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of paul.hartland at fsmail.net Sent: Wednesday, October 25, 2006 2:55 AM To: accessd; dba-sqlserver; dba-vb Subject: [AccessD] OT - Infragistics Ultragrid on Visual Basic 6.0 Form Importance: High To all, I have cross posted this as I don't know if that many of you out there would have used or still be using the Infragistics suite (mainly the UltraGrid). I have a grid with one of the columns set to a dropdown on the fly, and I create and populate the valuelist for it on the fly. This all works fine, I got to the employees record, click onto their training tab and it displays exactly what I want......BUT the problem is if I make a selection from the dropdown, it just nulls the training id all the time....All the help files I can find seems though I am doing this correctly but I must be missing something. If anyone out there thinks they may be able to help me, feel free to contact me on here or offline, as I have now been working on this for 3.25 hours and it is really starting to get to me :( Thanks in advance for all your help. Paul Hartland Paul Hartland paul.hartland at fsmail.net 07730 523179 -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com From fhtapia at gmail.com Wed Oct 25 17:44:44 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Wed, 25 Oct 2006 15:44:44 -0700 Subject: [dba-SQLServer] Weird Problem with SQL 2005 In-Reply-To: <20061024215520.27516.qmail@web88207.mail.re2.yahoo.com> References: <20061024215520.27516.qmail@web88207.mail.re2.yahoo.com> Message-ID: Arthur, When your system does a system restore what is it restoring, the registry? is IIS enbled for RS? Did you still have your folder in program files for sql server 2005? On 10/24/06, artful at rogers.com wrote: > I had to do a system restore on my box recently. HP makes this nice, since it stores the initial footprint on a read-only partitition. After reinstalling Windows, I then reinstalled SQL 2005 and Visual Studio 2005. When installing SQL 2005, however, the Reporting Services checkbox was greyed out. It wasn't that way before. Anyone got any idea why I can't install RS? I've poked around and I can't see anything amiss. > > TIA, > Arthur > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From artful at rogers.com Thu Oct 26 00:00:44 2006 From: artful at rogers.com (artful at rogers.com) Date: Wed, 25 Oct 2006 22:00:44 -0700 (PDT) Subject: [dba-SQLServer] Weird Problem with SQL 2005 Message-ID: <20061026050045.24064.qmail@web88211.mail.re2.yahoo.com> 1. An HP-box system restore deletes nothing but restores everything (OS etc.) as it was the day I bought the box. 2. I am not sure how to answer that question. In Control Panel it's installed etc. but I can't hit it from a browser using http://192.168.0.101 (which works from ping). 3. Yes, that folder is still there. Are you suggesting that I un-install then nuke that folder then re-install? I will do this if necessary. Fortunately, I always install the data to c:\sql rather than accepting the default, so no problem there. 4. Should I inspect the registry and destroy everything vaguely related to MS-SQL? Thanks for your attention to my problem. Arthur ----- Original Message ---- From: Francisco Tapia To: dba-sqlserver at databaseadvisors.com Sent: Wednesday, October 25, 2006 6:44:44 PM Subject: Re: [dba-SQLServer] Weird Problem with SQL 2005 Arthur, When your system does a system restore what is it restoring, the registry? is IIS enbled for RS? Did you still have your folder in program files for sql server 2005? On 10/24/06, artful at rogers.com wrote: > I had to do a system restore on my box recently. HP makes this nice, since it stores the initial footprint on a read-only partitition. After reinstalling Windows, I then reinstalled SQL 2005 and Visual Studio 2005. When installing SQL 2005, however, the Reporting Services checkbox was greyed out. It wasn't that way before. Anyone got any idea why I can't install RS? I've poked around and I can't see anything amiss. > > TIA, > Arthur > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From fhtapia at gmail.com Thu Oct 26 00:45:49 2006 From: fhtapia at gmail.com (Francisco Tapia) Date: Wed, 25 Oct 2006 22:45:49 -0700 Subject: [dba-SQLServer] Weird Problem with SQL 2005 In-Reply-To: <20061026050045.24064.qmail@web88211.mail.re2.yahoo.com> References: <20061026050045.24064.qmail@web88211.mail.re2.yahoo.com> Message-ID: if you nuke the folder you can user a product like ccleaner (avail from filehippo.com) and it should just re-install, just to test out the scenario i'm uninstalling Rs2005 / sql 2005 from my vm to see if I can reproduce the problem On 10/25/06, artful at rogers.com wrote: > 1. An HP-box system restore deletes nothing but restores everything (OS etc.) as it was the day I bought the box. > 2. I am not sure how to answer that question. In Control Panel it's installed etc. but I can't hit it from a browser using http://192.168.0.101 (which works from ping). > 3. Yes, that folder is still there. Are you suggesting that I un-install then nuke that folder then re-install? I will do this if necessary. Fortunately, I always install the data to c:\sql rather than accepting the default, so no problem there. > 4. Should I inspect the registry and destroy everything vaguely related to MS-SQL? > > Thanks for your attention to my problem. > Arthur > > ----- Original Message ---- > From: Francisco Tapia > To: dba-sqlserver at databaseadvisors.com > Sent: Wednesday, October 25, 2006 6:44:44 PM > Subject: Re: [dba-SQLServer] Weird Problem with SQL 2005 > > Arthur, > When your system does a system restore what is it restoring, the > registry? is IIS enbled for RS? Did you still have your folder in > program files for sql server 2005? > > > On 10/24/06, artful at rogers.com wrote: > > I had to do a system restore on my box recently. HP makes this nice, since it stores the initial footprint on a read-only partitition. After reinstalling Windows, I then reinstalled SQL 2005 and Visual Studio 2005. When installing SQL 2005, however, the Reporting Services checkbox was greyed out. It wasn't that way before. Anyone got any idea why I can't install RS? I've poked around and I can't see anything amiss. > > > > TIA, > > Arthur > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > > > -- > -Francisco > http://sqlthis.blogspot.com | Tsql and More... > _______________________________________________ > 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 > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More... From jwcolby at colbyconsulting.com Mon Oct 30 18:10:47 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 30 Oct 2006 19:10:47 -0500 Subject: [dba-SQLServer] Appending data to SQL Server table with identity field Message-ID: <002601c6fc81$04a17a30$657aa8c0@m6805> I am trying to append data from a CSV file to an existing table with a PK integer field (4 bytes) that is an identity, seed 1, increment 1. The append fails at the very end saying it can't append a null to the PK field. Does an identity not increment in the same manner that an autonumber does in Access? If so any ideas why this is failing? If not, any ideas how to cause this to happen. I hate to import to a table without the PK, and then append to the table with the PK. I have tried that and THAT does work. What is it about the import from CSV that is causing this failure? John W. Colby Colby Consulting www.ColbyConsulting.com From artful at rogers.com Mon Oct 30 18:50:35 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 30 Oct 2006 16:50:35 -0800 (PST) Subject: [dba-SQLServer] Appending data to SQL Server table with identity field Message-ID: <20061031005035.90507.qmail@web88208.mail.re2.yahoo.com> You say that it fails at the very end. That suggests that maybe there is a CRLF on the last line, and the failure occurs on the "next" line. Does the whole job abort when it hits the failure, or do you get all the rows but the last one, or what? Are you doing this with DTS? ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com; Access Developers discussion and problem solving Sent: Monday, October 30, 2006 7:10:47 PM Subject: [dba-SQLServer] Appending data to SQL Server table with identity field I am trying to append data from a CSV file to an existing table with a PK integer field (4 bytes) that is an identity, seed 1, increment 1. The append fails at the very end saying it can't append a null to the PK field. Does an identity not increment in the same manner that an autonumber does in Access? If so any ideas why this is failing? If not, any ideas how to cause this to happen. I hate to import to a table without the PK, and then append to the table with the PK. I have tried that and THAT does work. What is it about the import from CSV that is causing this failure? John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Mon Oct 30 20:00:54 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 30 Oct 2006 21:00:54 -0500 Subject: [dba-SQLServer] Raid controller Message-ID: <002b01c6fc90$66de1b40$657aa8c0@m6805> I purchased an Areca 1220 SATA 8 disk raid controller, with (7) Seagate 10.1 320 gb hard disks to create a raid system with. One of the disks was damaged and had to be RMAd. I went ahead and created a Raid 5 array using the 6 remaining drives. This gave me about 1.0 terra bytes on one volume and about 370 gb on another volume, both Raid 5. I just received the RMAd drive back, popped it in, added it to the array and told the controller to convert to Raid 6 for both volumes. That was early this afternoon, and the controller has finished the conversion of the large array to Raid 6 and is about 50% finished converting the smaller array to Raid 6, all consuming ZERO CPU and doing so while I was using the arrays pretty heavily. The controller is also very fast. Raid 5/6 writes are about the speed of the individual drives and reads are much faster (~raid 0 speed according to Areca) These disks are about $95 from Newegg and can be purchased with free shipping if you keep your eyes open so that is a real $95 / disk. This particular controller is currently about $500. This made my actual cost about $1200 for 1400gb in a Raid 6 config. Someday I hope that the Seagate 10.1 750 gb drives drop into this price range in which case I will upgrade. ATM those drives are about $375-$400 each which makes them out of my range. I am impressed with this Areca controller which is the point of this email. Areca makes controllers that handle various numbers of disks. The controller uses a PCI-X8 connection to the CPU so you must have a PCI-X capable motherboard. If you need more disks, they also have a 12, 16 and 24 disk controller, for more money of course. Nice controller so far! John W. Colby Colby Consulting www.ColbyConsulting.com From jwcolby at colbyconsulting.com Mon Oct 30 20:24:18 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Mon, 30 Oct 2006 21:24:18 -0500 Subject: [dba-SQLServer] Appending data to SQL Server table withidentity field In-Reply-To: <20061031005035.90507.qmail@web88208.mail.re2.yahoo.com> Message-ID: <003001c6fc93$ab8574c0$657aa8c0@m6805> There almost assuredly is a CRLF at the end of the last line. The whole job aborts, no lines are appended to the table. I am doing this with the "data import / export wizard". The odd part to my mind is that there are three new fields that are in there which will in the future be "match code" fields, which are allowed to be null, and which are indeed set to null. The fourth PKID field which is supposed to be an Integer / primary key, identity fails. My uneducated guess is that the entire batch is queued up or read in, then at the very end, SQL Server tries to actually start appending data. At which point it tries to stuff a null into this field, which by definition cannot be null, and since the "first record" that it attempts to actually create fails, the whole batch fails. I guess my question is, why is it trying to stuff a null into that field. I don't specify any data at all for that field, in fact that field does not even exist in the source csv file. My expectation is that SQL Server's identity widget would kick in and create the incrementing integer. Apparently this does not happen and since the field itself is not even specified the wizard tries to fill in the extra fields at the end with null values. It succeeds nicely with the extra fields which are text and can accept null values. I know this because if I try the same process without the PK field in the destination table, the data does successfully import. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Monday, October 30, 2006 7:51 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Appending data to SQL Server table withidentity field You say that it fails at the very end. That suggests that maybe there is a CRLF on the last line, and the failure occurs on the "next" line. Does the whole job abort when it hits the failure, or do you get all the rows but the last one, or what? Are you doing this with DTS? ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com; Access Developers discussion and problem solving Sent: Monday, October 30, 2006 7:10:47 PM Subject: [dba-SQLServer] Appending data to SQL Server table with identity field I am trying to append data from a CSV file to an existing table with a PK integer field (4 bytes) that is an identity, seed 1, increment 1. The append fails at the very end saying it can't append a null to the PK field. Does an identity not increment in the same manner that an autonumber does in Access? If so any ideas why this is failing? If not, any ideas how to cause this to happen. I hate to import to a table without the PK, and then append to the table with the PK. I have tried that and THAT does work. What is it about the import from CSV that is causing this failure? John W. Colby Colby Consulting www.ColbyConsulting.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 From artful at rogers.com Mon Oct 30 22:09:41 2006 From: artful at rogers.com (artful at rogers.com) Date: Mon, 30 Oct 2006 20:09:41 -0800 (PST) Subject: [dba-SQLServer] Appending data to SQL Server table withidentity field Message-ID: <20061031040941.29485.qmail@web88201.mail.re2.yahoo.com> So you have tthree paths: instant success, or this puzzle in chunks or all at once.. Approach 1: 1. Create an incoming table with no Identity key 2. Inhale the data. 3. Create a separate DTS task to import the inhaled data to the real table, with Identity key. 4. Package the whole thing into a single DTS task or job, and schedule it accordingly. Approach 2: 1. Commit the Inhale at a specific number of rows, ideally an even division (or mod(1) of the total number of rows) 2. Run what you have and see where it breaks. Could be the last line, could be an errant line somewhere in the middle. At least you inhale all the rows up to the last commit. Approach 3: 1. Much around with the text file looking for oddities that could cause this to happen. My choice is Approach 1, on the grounds that the most important thing is to acquire the data. Importing into a non-Identity table ought to be quick, and also ought to reveal a problem somewhere in the text file. Once you have it in a temp table that SQL considers valid, then it's trivial to append the rows to the actual table. The whole multi-step process can become a single DTS task or job, scheduled if you wish, and buy you time to figure out exactly what's wrong with the input file. Arthur ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com Sent: Monday, October 30, 2006 9:24:18 PM Subject: Re: [dba-SQLServer] Appending data to SQL Server table withidentity field There almost assuredly is a CRLF at the end of the last line. The whole job aborts, no lines are appended to the table. I am doing this with the "data import / export wizard". The odd part to my mind is that there are three new fields that are in there which will in the future be "match code" fields, which are allowed to be null, and which are indeed set to null. The fourth PKID field which is supposed to be an Integer / primary key, identity fails. My uneducated guess is that the entire batch is queued up or read in, then at the very end, SQL Server tries to actually start appending data. At which point it tries to stuff a null into this field, which by definition cannot be null, and since the "first record" that it attempts to actually create fails, the whole batch fails. I guess my question is, why is it trying to stuff a null into that field. I don't specify any data at all for that field, in fact that field does not even exist in the source csv file. My expectation is that SQL Server's identity widget would kick in and create the incrementing integer. Apparently this does not happen and since the field itself is not even specified the wizard tries to fill in the extra fields at the end with null values. It succeeds nicely with the extra fields which are text and can accept null values. I know this because if I try the same process without the PK field in the destination table, the data does successfully import. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Monday, October 30, 2006 7:51 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Appending data to SQL Server table withidentity field You say that it fails at the very end. That suggests that maybe there is a CRLF on the last line, and the failure occurs on the "next" line. Does the whole job abort when it hits the failure, or do you get all the rows but the last one, or what? Are you doing this with DTS? ----- Original Message ---- From: JWColby To: dba-sqlserver at databaseadvisors.com; Access Developers discussion and problem solving Sent: Monday, October 30, 2006 7:10:47 PM Subject: [dba-SQLServer] Appending data to SQL Server table with identity field I am trying to append data from a CSV file to an existing table with a PK integer field (4 bytes) that is an identity, seed 1, increment 1. The append fails at the very end saying it can't append a null to the PK field. Does an identity not increment in the same manner that an autonumber does in Access? If so any ideas why this is failing? If not, any ideas how to cause this to happen. I hate to import to a table without the PK, and then append to the table with the PK. I have tried that and THAT does work. What is it about the import from CSV that is causing this failure? John W. Colby Colby Consulting www.ColbyConsulting.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 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com From jwcolby at colbyconsulting.com Tue Oct 31 10:20:43 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Tue, 31 Oct 2006 11:20:43 -0500 Subject: [dba-SQLServer] SQL Server observed performance Message-ID: <000a01c6fd08$849b1700$657aa8c0@m6805> I thought you guys might find this interesting. I have a database that I imported a couple of years ago. On a single processor 3 ghz AMD64 running 2 mbytes of memory, using (4) individual IDE 250gb hard drives (no raid) the system would import ~ 1000 rows per second into SQL Server. Each text file was ~10 gbytes, consisted of ~700 fields and 3 million records per file. Each field was originally padded right with spaces (comma delimited, but fixed width). This time around, I built an Access (really just VBA) preprocessor to open each file, read it line by line, strip all of the padding off the left and right sides (there was some left padding as well) and write it back out to another file. This dropped the average text file size to ~ 6.5 gbytes, which leaves us with average padding of well over 35%. It also left the resulting data in the unpadded after importing into SQL Server which makes sorts / searches and indexes possible. Anyway, after stripping all of this padding and building new files, I am now importing these into my new server which is a AMD64 X2 dual processor 3.8 ghz with 2 gbytes of ram. The disk subsystem is now a pair of volumes hosted on a raid 6 array, 1 tbyte for the main data store and ~400 gb for the temp databases. The new system imports the new (stripped) data files at about 3000 records per second. I have to run 3 imports at a time to keep both cores above 90% usage. Running 3 imports at a time, the imports happen roughly at 2k records / second FOR EACH IMPORT. Oddly, if I run more than 4 imports at a time, the processor usage drops back to ~70% for some reason and in fact each import slows to ~500 imports / second. This may have to do with the limits of disk streaming off of the machine that holds the source text files. The source files come from a second machine, all the files on the same disk / directory, over a 1ghz network (switch). I am happy to say though that the new dual processor server appears to be able to perform this specific task ~3 to 6 times as fast which is a huge and much needed performance boost. The other advantage to this configuration is that I am no longer playing games splitting the database up into smaller files residing on individual hard drives, and of course, the whole thing is using raid 6 which provides much needed security. John W. Colby Colby Consulting www.ColbyConsulting.com From jwcolby at colbyconsulting.com Tue Oct 31 23:12:02 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 1 Nov 2006 00:12:02 -0500 Subject: [dba-SQLServer] What is going on Message-ID: <001b01c6fd74$447fd5e0$657aa8c0@m6805> This afternoon, soon after posting how fast the system is, SQL Server "locked up". I had imported 18 files over the afternoon, and then suddenly the three that were processing just froze. In task manager I would see SQL Server activity, the processors would alternate between no activity and 50% utilization, and when that happened SQL Server was the task using the CPU time. However NO records were importing. I decided to let it run, went away for a meeting, returned several hours later to find NO cpu activity and the exact same number of records imported (still frozen). I aborted, then restarted a single import process. It progressed, but slowly. The next progressed but even more slowly. The last file that needs to be imported is just dragging. As in will take 12 hours or more to do just the one file (20 minutes was the average before). I stopped that last process, moved the file physically out onto the smaller raid to test whether it was a comms issue between machines. No help. My C: (system) drive has about 10g out of 80 used. My D: (SQL system databases there) has about 10g used out of 200 total. My E: drive (the main database file for this database) has used 298 G with 901 gig free (one of two Raid 6 drives) . My F: drive (the main database log file for this database) has used 45 Gb with 330gb free (the second Raid 6 drive). I have huge amounts of free space on the raid drives, well over 700 gb on the one, and 300 gb on the other. The main db file is now up to about 280 mb but by my calcs that is about normal (correct) given the amount of data input so far. At this point I am on the last file to import, sitting at about 1 million records imported out of 3 million to be imported. It is importing them about 1000 records every three seconds. There are about 63 million records in the table. No indexes, no triggers, nothing like that. Just raw data. This thing should be flying. Instead it is crawling. CPU usage is running 12% to 25%, with SQL Server.exe and MMC.exe using that. What the heck is going on? John W. Colby Colby Consulting www.ColbyConsulting.com From jwcolby at colbyconsulting.com Tue Oct 31 23:27:14 2006 From: jwcolby at colbyconsulting.com (JWColby) Date: Wed, 1 Nov 2006 00:27:14 -0500 Subject: [dba-SQLServer] What is going on In-Reply-To: <001b01c6fd74$447fd5e0$657aa8c0@m6805> Message-ID: <002001c6fd76$64323ca0$657aa8c0@m6805> Just an update, I started a new import wizard processing the exact same file (a copy on the E: drive) into an empty table and it is running at the expected 3000 records / second, so far. So it appears to have something to do with the number of records already in the main table as opposed to a general SQL Server slow down, raid drive slowdown etc. I am canceling the sloooow import. The import into a clean table should be finished within 15 minutes or so, at which point I will try an append from the smaller table and see if that happens quickly. Something funky is definitely going on though. The cancel takes a long time, and while that is happening, the other data import has slowed to a crawl. This really sucks! John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Wednesday, November 01, 2006 12:12 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] What is going on This afternoon, soon after posting how fast the system is, SQL Server "locked up". I had imported 18 files over the afternoon, and then suddenly the three that were processing just froze. In task manager I would see SQL Server activity, the processors would alternate between no activity and 50% utilization, and when that happened SQL Server was the task using the CPU time. However NO records were importing. I decided to let it run, went away for a meeting, returned several hours later to find NO cpu activity and the exact same number of records imported (still frozen). I aborted, then restarted a single import process. It progressed, but slowly. The next progressed but even more slowly. The last file that needs to be imported is just dragging. As in will take 12 hours or more to do just the one file (20 minutes was the average before). I stopped that last process, moved the file physically out onto the smaller raid to test whether it was a comms issue between machines. No help. My C: (system) drive has about 10g out of 80 used. My D: (SQL system databases there) has about 10g used out of 200 total. My E: drive (the main database file for this database) has used 298 G with 901 gig free (one of two Raid 6 drives) . My F: drive (the main database log file for this database) has used 45 Gb with 330gb free (the second Raid 6 drive). I have huge amounts of free space on the raid drives, well over 700 gb on the one, and 300 gb on the other. The main db file is now up to about 280 mb but by my calcs that is about normal (correct) given the amount of data input so far. At this point I am on the last file to import, sitting at about 1 million records imported out of 3 million to be imported. It is importing them about 1000 records every three seconds. There are about 63 million records in the table. No indexes, no triggers, nothing like that. Just raw data. This thing should be flying. Instead it is crawling. CPU usage is running 12% to 25%, with SQL Server.exe and MMC.exe using that. What the heck is going on? John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com