December 12, 2011 at 3:42 am
Hi all
I was looking through the documentation for service packing SQL 2008 R2. I couldn't see mention of backing up the mssqlsystemresource.mdf database. Does this need to be done before service packing, what are peoples thoughts?
Many thanks
December 13, 2011 at 8:57 am
On startup SQL Server reports "the resource database build version" and it seems as important as ever. The main difference in SQL2008 is the location of the resource db, which they have treated even more like a binary executable (it is in Binn), and which cannot be moved.
After installation and service packing I still stop SQL Server to take copies of the system database and the mssqlsystemresource files, to save for recovery purposes. So taking copies before Service packing would be belt-and-braces, and taking them after service packing/cumulative updating is an absolute must.
December 13, 2011 at 9:23 am
Why a must after the update, does updating break the log chain?
December 14, 2011 at 6:09 am
Nothing to do with a log chain: the resource database is specific to the SQL Server Build (and I believe has to keep version in step with the master db), so anything that changes the Build (Service Pack, Cumulative Update) means a change to the resource db - so you have to take a fresh copy in case you need to rebuild the installation. There comes a point where you may as well be reinstalling and reapplying patches, but if you can rescue an installation where files or drives have suffered damage or corruption, it can be quicker and less intensive than starting over.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply