November 15, 2006 at 10:55 am
Hi everyone, I have "aquired" a clustered SQL Server 2000 instance with SP3a. This holds around 30 databases for some 20+ applications.
Server is stable and file placing optimized for performance. There are no DEV environments for most databases.
I am currently standardizing this server and welcome any comments with regards to upgrading to SP4. I generally tend to think "if it aint broke dont fix it". But cant help be afraid that sometime in the future something wil go wrong and the fix will be SP4!!!
Any comments, views or general approaches others have taken will be very welcome.
Siz
November 16, 2006 at 7:53 am
SP4 is a good idea just because there is no more support for SP3. No QA is dangerous though.
where i work they did a SP2 to SP3 upgrade a few years ago and everything stopped working because of jdbc issues.
November 16, 2006 at 10:45 am
If the environment is stable then I would leave it alone for the time being. The idea of no support for SP3a is not quite correct. If you have an issue that is causing a problem then I would consider upgrading. But by all means yell and scream for a devlopment or testing environment. You do need one, not eventually, now !
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
November 17, 2006 at 3:49 am
SQL Noob, that is exactly what I am afraid of! Upgarde to SP4 then...SPLAT!
Rudy, I totally agree with you. I think in the past what has happend is that whenever a problem occured which suggested a bug fix, the database in question was moved off to a diffferent server. As with the nature of this client (I wrk consultancy thus many clients) there is not much info on any of the application DB's as all systems were inherited. Getting a working test server for all the databases would be a pretty hefty task and a lot of guesswork!
I will continue to replicate as many DB's as I can! Any other thoughts, experineces, opinions on this topic are welcome.
Regards
Siz
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply