September 26, 2002 at 9:24 am
Hi all,
I'm installing a DB with VB front ends on a client's SQL Server 7.0 box running on NT 4.0 Server. I checked, and they are running the base version of SQL Server 7.0 with NO service packs (yikes!). Fortunately for them, it's been stable all this time. My question: When I get there to create my DB and such, would it be safe to install SP3 first, THEN proceed with my project? In other words, is the SP3 install on a base version fairly safe (of course we'll do full backups first), or should I not take a chance with their world, and just go do my install? If SP3 is safe to do, does SP1 or SP2 have to go first?
Thanks!
Paulie
September 27, 2002 at 4:20 am
I would never install any Service Pack on a production server without first testing on a development server. Until you test you won't know how the application will react to the upgrade. There are many significant changes made in the various Service Packs, including changes to core pieces of SQL Server that could change the way SQL Server executes stored procedures and T-SQL statements. In most cases these changes are for the best, but sometimes code must be rewritten to avoid SQL Server executing it slower than it used to.
I think SP3 has all the changes made in SP1 and SP2, but I am not sure.
Robert Marda
SQL Server will deliver its data any way you want it
when you give your SQL Programmer enough developing time.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
September 27, 2002 at 11:32 am
Good advice... thanks!!!
September 27, 2002 at 12:00 pm
In addition, boxes behave differently no matter how well you test with similar everything. Little power fluctuations or unknown process running can mean a locked file hendering the upgrade or sending it afoul. Makre sure you create a full backup of the sever before you proceed unless you are comfortable with working any issue that may arise. Also, have a set of testing parameters setup to make sure the box is up to par with your expectations after the upgrade, but keep in mind early execution of SQL is slower than after it has run several times, so take that into account. Now as for SQL realease to SP3 it is just fine. You may even want to go ahead with SP4.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
September 27, 2002 at 12:29 pm
Amen. I appreciate the insight. No way I'm going to throw on that servoce pack and hope. After my install and once that's stable, I'll approach them for a designated upgrade release, with test data ready to go.
Thanks again for the fast replies, both of you.
Paulie
September 30, 2002 at 9:31 am
Check out SP4 available from MS since April 2002. http://www.microsoft.com/sql/downloads/sp4.asp
"Because SQL Server Service Packs are cumulative, SP4 includes all fixes from previously released Service Packs, and can be applied to an original installation or to one where Service Pack 1 (SP1), Service Pack 2 (SP2), or Service Pack 3 (SP3) was previously applied."
Make sure that your sa password is not blank,
or SP3/SP4 will change your security mode to Windows only.
Yul
Yul Wasserman
September 30, 2002 at 11:51 am
Thanks Yul. For Pete's sake, why doesn't the install wizard just PROMPT you for an Admin password, and do away with the blasted sa bit, right?
: )
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply