Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Physical Properties of Resource The physical file names of the Resource database are mssqlsystemresource. Warning Upgrades and service packs sometimes provide a new resource database which is installed to the BINN folder. Important After restoring a backup of mssqlsystemresource.
Is this page helpful? Fetching it from the another instance with same version? It does not contain any user data or user related metadata, so In theory copying it from another working instance with same patch level will be fine and should not cause issues. As per BOL "After restoring a backup of mssqlsystemresource.
Though I dont remember doing this while I had to a couple of years back, its good to do the updates just in case some inconsistency occurs. For "I also tried i moving to same location and I did it successfully I am sure you are making some mistake. Are you sure you did the testing in instead of ? As you said resource DB is corrupt that can be issue. Ok if I agree that you are saying correct that both files cannot be at same location you must be getting error when starting SQL Server can you post that.
It would be located at. What do you exactly mean by not changeable BOL also says that you cannot change it but in other doc says you should move it to location of master DB, confusing!!!
I just moved resource database from binn to different location. I recall when was released that MS stated something along the lines of "resource db is now in binn and it cannot be changed". I haven't actually tried to move resource db since , and I haven't seen the documentation where it states that it can be where master is. Or perhaps SQL Server quite simply uses sys. The underlying tables, of course. In , if I move the mssqlsystemresource to the same folder as Master, the error message is "FileMgr::StartLogFiles: Operating system error 2 The system cannot find the file specified.
And in and since it has to be in the binn catalog not changeable. Hi Shanky,. Michael CS thanks for pointing this out. I had a doc bug filed. I was also about to : , but before doing that I mailed directly to Elite Group get response still not got it.
Balmukund : Oh no. By replacing file you would introduce version mismatch between SQLServr. Balmukund : No, that information is not correct. During the whole upgrade process replacing file is just one of the step.
Who would take care of unregistering DLLs, keeping back old version of files etc? Balmukund : There are two possible options. First and the easiest one is to copy the resource database files from another instance that is the same version, service pack, cumulative update patch level is very important. This should only be done on an isolated test instance and will allow you to easily view the system objects in the mssqlsystemresource database using SSMS.
You cannot find it using SSMS. The physical file location of resource database for versions SQL Server and later is. In SQL Server users were allowed to copy the resource database off to another location when they moved master database files. The Resource database depends on the location of the master database. If you move the master database, you must also move the Resource database to the same location. Since it was documented so users started moving it and playing around with it by moving to the different location.
This has repercussions though many users complained that after moving resource database when they tried applying a service pack or CU update it failed. The failure caused in SQL Server service pack upgrade which was eventually caused by movement of resource database location led to change in resource database location and it was decided that resource database would reside in the BINN folder along with the rest of the binaries.
Also, users would not touch files present in BINN folder. Sign up to join this community. The best answers are voted up and rise to the top.
0コメント