Moving master,msdb and model dbs
-
Initially SQL Server is installed on a server and the application databases placed on that server. As time went by the application databases grew till they swallowed the space.
Technical Support then provided us with space on a filer and (with the filer software) moved the application databases onto the filer. The SQL Server thinks that the application databases are sitting on a new drive on the initial server. The SQL Server program files remain on the original server.
My colleague also moved the master, model and msdb databases to the filer. Recently I had to move a very large application database to the filer but I did not move the master, model and msdb databases; I have vague recollections of being told that I should touch these unless absolutely necessary.
Can the master, model and msdb databases be moved to the filer and what is the effect of doing so? I thought that these databases are accessed by programs etc and should not be moved.
Madame Artois
-
They can all be moved and are covered in technet, it takes a bit of stopping and starting of services. I think this is the kb number KB224071
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/ -
Having read this kb I'm not sure that my colleague did it this way; the filer software may have just moved it. She might have just attached and re-attached the databases; I don't know what order.
What's the 'worst case scenario' and how do we check to see it the worst has happened?
Madame Artois
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply