April 27, 2012 at 10:51 am
Greetings folks...
I have inherited... a network and infrastructure that is in sore need of modernization.
I have a requirement to upgrade a single instance of SQL Server 2005 RTM :
Microsoft SQL Server Management Studio9.00.1399.00
Microsoft Analysis Services Client Tools2005.090.1399.00
Microsoft Data Access Components (MDAC)2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML2.6 3.0 6.0
Microsoft Internet Explorer8.0.6001.18702
Microsoft .NET Framework2.0.50727.3625
Operating System5.2.3790
I have done a little research and it appears that with the Service Packs being cumulative, this should be "relatively" painless. However, in my experience with Microsoft, this is rarely the case.
Would any of you have insight, and/or input that could assist me in making this as straight forward as possible?
Thanks!
April 27, 2012 at 11:48 am
It should be painless, should be. I have installed SQL 2005 SP4 many times and never had an issue, but know that it is not uninstallable, so your rollback plan is going to be either restore a complete image of the server, or rebuild. Either way make sure you have DB backups that you verify can be restored, and all the relevant installer binaries (including Windows and all its patches) ready in case you do have to rebuild the server from scratch.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 30, 2012 at 7:35 am
Thanks for the advice!
It went off without a hitch.
In fact, it downloaded and installed SP4 without waiting for intervention. That kind of freaked me out.
Luckily I had everything backed up and restorable prior to kicking off the download.
May 1, 2012 at 9:39 am
Also, use something like http://sqlserverbuilds.blogspot.com/%5B/url%5D to keep track of all the builds. Look at each CU and other for your SP, and see if you want to apply it or not.
For SQL 2005 in specific, note that build 5292 addresses MS11-049, which is a security update. We patch all of our SQL 2005 instances to this build level.
May 1, 2012 at 11:33 am
Typically you should backup all databases before you apply any SP or CU. I also stop the SQL Server services and backup the master, msdb, model .mdf and .ldf files as well.
One other thing to do is to stop all unnecessary services on the server. Microsoft has gotten better with each version/upgrade of checking for services during preinstall and warn you to stop them before installing. I usually stop backup software, AV, IIS, WWW stuff. Anything that isn't Windows required.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply