Moving master, having problem
-
We set up a test box and having been trying to move an entire instance
from our production server to this one. I have moved all my created
dbs using the RESTORE WITH MOVE. Now I am trying to move the Master,
Model, and msdb. This is where I am having trouble. On the production
box the dbs are stored on D:\mssql$instancename\data. On the test
server the data is stored in C:\Program Files\Microsoft SQL
Server\mssql$instancename\data. Also the server names are different.
So I finally got the Master from production to restore over the test's
copy. Now the instance will not start. I was trying to use the
following code in cmd line to connect to the instace so I could then
copy model and msdb:
sqlservr -c -f -T3608 -T4022 -sINSTANCENAME
When this is trying to connect I read it is failing and saying that the
MDF and LDF may be corrupt or not there. The problem is it is now
trying to look in D:\mssql$instancename\data instead of C:\Program
Files\Microsoft SQL Server\mssql$instancename\data. Any ideas on how I
can change this, or if I have to reinstall the entire instace, not run
into this again?
-
this is how you move system dbs (master, model and tempdb):
http://support.microsoft.com/kb/224071/
* Noel -
That article shows if you are moving the mdf and ldf, not restoring from a bak file correct? I am using a bak file to move all the data to the test box.
-
as long as you don't have stored procedures of your own you should not need to restore master at all mdb files and ldb files should be sufficient because this is the first db you move the the restore process (with move) will update master as you go. the Master bak file should be intended for the SAME server.
Because you are stuck now I would try to create a "D:" drive using the good old subst command create the foler there and move the master files onto it. once you get it to boot then follow the correct procedure for moving master and you should be OK. By the way dont for get to remove the path ceated with subst
Hope this help
* Noel -
you can start SQL from the command prompt using the path arguments to point to the folder that contains the master database you wan to use. Once you have the instance working, change the startup parameters in the server properties to point to the correct folder.
see BOl topice for the sqlservr application.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply