June 17, 2013 at 10:40 pm
Years ago we installed a sql server service pack on a non-clustered server and the results were usually fine. Now they want a fallback plan in case the service pack install fails. This is a good idea but I'm not sure what comprises a good fallback plan for sql. (Uninstall the service pack -- never done that before. We can start by backing up all databases but restoring them, including the system databases, will be time consuming. Maybe we should image the entire server to trim the restoration time.)
Any thoughts you have on this matter will be appreciated.
TIA,
Barkingdog
P.S. I presume a sql service pack can possibly update\modify both system and user databases.
June 18, 2013 at 5:31 am
As far as I know - as of 2005 a service pack cannot be uninstalled - I might be wrong here.
If possible, backup the entire image of the server before the service pack installation.
My usual steps are, besides the above:
Make sure all DB's have current backups
Backup system databases
Stop SQL Services and copy out the system DB's
June 18, 2013 at 3:03 pm
If this is a VM you could take a snapshot before the SP install. If it goes south recovery is easy just don't delete the snapshot until your sure the SP is good.
If not then you need good backups (I usually stop SQL and make a copy of the system DB's as an extra backout option as copy/paste is easier than restoring the system DB's). If issues then uninstall SQL, re-install to the same location, service pack to the same level before the update, stop sql services and copy the system containers back, start SQL!! Or you can re-install and service pack, start SQL in single user mode and restore system DB's then start sql normally and attach user DB's.
June 18, 2013 at 7:59 pm
DeWayne_McCallie,
>>>>I usually stop SQL and make a copy of the system DB's as an extra backout option as copy/paste is easier than restoring the system DB's
Ha! I didn't think of that very sensible item. I will do that from now on.
Thanks,
Barkingdog
June 19, 2013 at 1:13 am
If it is 2008+ you can uninstall using Programs and Features just like a hotfix uninstall. If it is 2005- you will need to uninstall/reinstall.
Backups of system/user databases are required in both scenarios though.
Uninstalling a SQL Server Service Pack
Joie Andrew
"Since 1982"
June 24, 2013 at 3:16 pm
If you really want a good fallback plan, the gold standard is a drive image; whether that's a vRanger backup of a VMWare VM, or a Paragon/Acronis TrueImage/DD/Clonezilla/Norton Ghost image of a physical box, or even a Parted Magic copy of a partition, it's a way of doing a bare-metal restore to exactly the state you were in prior to the image.
Note that for the commercial options, it's usually several hundred dollars per Server OS.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply