Lee posted on April 9, 2008 10:47

The Resource Database – leave it alone!

When separating data and log files, you might think that moving the Resource database (mssqlsystemresource.mdf and mssqlsystemresource.ldf) is a good idea. Suggestion – don’t move it. So, you’re concerned about I/O, and synchronous/asynchronous activity? I wouldn’t be. Moving this is probably a waste of time, and there is one huge gotcha that you need to be aware of if you do. In BOL, it states that

If you move the master database, you must also move the Resource database to the same location as the master data file.

What happens if you don’t? I don’t have an exhaustive list, but what I did learn is that when I tried to apply a service pack, the log file got overwritten. The new log file did not match the data file, and the install was history. I probably could have tried to find a workaround (sp_attach_singe_file_db?), but opted to reinstall. If you decide to move it, as I did (dorking around with it), make sure and leave both the data and log files with master.mdf!

Lee

 

-------------------------


Amazing what is stuck in the fine print of Books Online

  

 


Comments

Add comment




  Country flag

biuquote
  • Comment
  • Preview
Loading




by Lee Everest, M.S.

Search


Ads

Calendar

«  July 2010  »
MoTuWeThFrSaSu
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678
View posts in large calendar

Tags

Disclaimer
The opinions, code, examples, et.al. expressed herein are my own personal opinions and do not represent my employer's view in any way, shape form, or fashion.  All code for demonstration purposes - no guarantees, either written or implied, are made.

© Copyright 2010 Lee Everest's SQL Server, etc. weblog