February 11, 2015 at 5:03 am
Hi folks.
Copy mssqlsystemresource.mdf of a recently upgraded server and paste to an old
server have same effect of upgrading via .exe installation?
Is anyone trying this method without problems after that?
My idea is to save time and administrative efforts in upgrades (Service Packs and/or Cumulative Updates) using this method.
According to BOL:
The Resource database makes upgrading to a new version of SQL Server an easier and faster procedure. In earlier versions of SQL Server, upgrading required dropping and creating system objects. Because the Resource database file contains all system objects, an upgrade is now accomplished simply by copying the single Resource database file to the local server.
Thanks in advance for any help you are able to provide.
February 11, 2015 at 5:16 am
No, it won't.
BoL is talking about as part of a patch, the patch installation process can just replace the resource DB with an updated one instead of having to run a whole pile of schema scripts.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 11, 2015 at 6:32 am
moving a later version of the resource database will also stop a patch of the same version installing if its ever needed. I faced this very same issue sometime ago on a system that was pre deployed and was having issues
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 11, 2015 at 10:39 am
Gail,
Makes sense. My doubt was a misunderstanding after all.
Perry,
Good to know about your experience. It's an interesting situation.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply