Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dbthj
Posting Yak Master
143 Posts |
 Posted - 2012-01-19 : 13:40:08
|
| I am testing procedures for moving system databases in a 2005 instance. I found on the web 3 separate sets of instructions for doing this. All 3 contain a step that says to alter the resource database to read_only at one point. None of them say to later alter it to read_write. Is that the way it is done? Really? Make it read_only and leave it that way? I'm not sure what a resource database does, but I would imagine it updates stuff once in a while. |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-01-19 : 13:46:33
|
| If this is the database you're referring to: http://msdn.microsoft.com/en-us/library/ms190940.aspxThere's no reason to move it, and as the article states, you shouldn't try to do anything to it except on the advice of Microsoft Customer Support. |
 |
|
|
dbthj
Posting Yak Master
143 Posts |
Posted - 2012-01-20 : 16:16:51
|
| That article is for SQL 2008 R2. In 2008, the resource database cannot be moved. This is SQL 2005. It can be moved and Microsoft has no problem with that. I found out that the read-only status is ok for the resource db. It is never updated except at upgrade time when it is replaced. |
|
|
|
|
|
|
SQL 2005 Move System DBs - Resource DB Read-Only