October 21, 2005 at 12:04 pm
I recently got a new server to replace an old one. I restored almost all databases and then restored the old master. When starting in single user mode, it says it cannot find the dbs that I didn't restore and just dumps me back to cmd line (doing a sqlservr -c -m) . Well, simply I dropped those dbs from the old server, rebuilt master to get sql at least to start and restored master again. Now sql starts up aok.
For next time, is there any way to get sql to disregard dbs and their associated files it cannot find so it can start and then I can drop those dbs I don't need?
October 21, 2005 at 1:58 pm
We would normally get a suspect database status when the database file does not exist.
The sequence: normally you would restore Master and MSDB first, then restore or re-attached user databases, see "Planning for Disaster Recovery" article in Books Online. There is a sequence at the end of the article.
I have another way with replacing data directory but it would work only with the identical setup, file path and SP/Patch level.
Regards,Yelena Varsha
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply