February 22, 2002 at 1:59 am
Folks,
Just had me admin on the phone asking me my advice on an sp2 install. We have no sps installed at the minute. Any advice? One caveat. The server is case_senstive due to a requirement for a certain hr app. Dont ask.
February 22, 2002 at 4:31 am
I always suggest going with the SP as there are numerous issue including security related fixes in them. To get a better idea of what the SP does, check out Microsofts SQL website and look at the SP's fix list (both SP1 and SP2). But before I put it on a production server, test it, backup the production server, then install it that way if you run into issues you have a way out.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
February 22, 2002 at 4:33 am
Before applying any new service pack, I first find out what bug fixes and changes the service pack is going to give me. This way I can better determine if I need the service pack now or can wait a little longer.
Once I've decided I am ready to apply the service pack I apply it in our development environment to see how it affects everything and if I am applying it with the hope it will fix a problem I have then I check to see if it really helped or not. Then I apply it in our testing environment so that more extensive testing can be done. Only after that do I apply a service pack to our production SQL Servers.
Last, I usually wait 6 months after a service pack is released before planning to apply it on our SQL Servers. I wait to see if there are any problems with the Service Pack. My philosophy is let someone else find the problems and Microsoft fix them before I risk having them.
So, if you are talking about the service pack for SQL Server 2000. I would wait a few months longer before applying it, unless you have a problem that the SP should fix and you must have it fixed ASAP.
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
February 22, 2002 at 10:03 am
I tend to agree with Robert. Personally, I'm at SP1 (ss2k) and SP2 (sql7). Luckily we have Brian here who does extensive beta testing and reports feedback here.
I install on dev, test for a couple weeks, move to QA, give a couple weeks and then go to production. It's nice to be at the right level in case you have issues. However, my v7.0 server has not had any issues in over a year, so setting up a test v7 server and testing the sp isn't worth it.
I don't wait 6 months, more like 1-2 months.
Steve Jones
February 22, 2002 at 10:43 am
I'm trying to set up a process similar to what Steve describes. Until a service pack is tested with the existing install base, it's impossible to say if there is a conflict. Things that shouldn't have anything to do with one another could suddenly get affected.
We saw this with VB 6.0 SP5, and Content Management Server. Something in SP5 breaks drag and drop functionality for CMS. It took us two weeks to hash it through with Microsoft, including shipping images of systems, etc., and that's what it ended up being. Who would have thunk it?
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply