Re: Restore Master DB to New Server
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 03/25/04
- Next message: Cory: "Re: Restore Master DB to New Server"
- Previous message: Tibor Karaszi: "Re: Limiting access to certain DB's"
- In reply to: Cory: "Re: Restore Master DB to New Server"
- Next in thread: Cory: "Re: Restore Master DB to New Server"
- Reply: Cory: "Re: Restore Master DB to New Server"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Mar 2004 17:37:25 +0100
Yes, the user database will be suspect. Just drop them and then do the restore (or attach).
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp "Cory" <anonymous@discussions.microsoft.com> wrote in message news:DF1DC370-0156-4EE8-B80C-8FA56EE08B60@microsoft.com... > Okay, I looked at where the system databases are, and they are on the same path. I restore the Master via command line utlity, and once the master is restored, it kills that connection. I attempt to reconnect to restore the other DB's, and it gives an error for each and every user DB stating: > > Timestamp Spid X Starting up database 'db'. > Timestamp Spid X udopen: Operating System Error 2(The system can not find the file specified.) during the creation/opening of physical device f:\microsoft sql server\mssql\data\db.mdf. > Timestamp Spid X FCB::Open failed: Could not open device f:\microsoft sql server\mssql\data\db.mdf for virtual device number (VDN) 1. > Timestamp Spid X Device Activation error. The physical file name 'F:\microsoft sql server\mssql\data\db.mdf' may be incorrect. > > I have looked through the other reply you sent, and that seems to appear that if you have the DB to reattach, all I have are the backup files. > > My thinking is correct, right? Restore Master first...then msdb, and then user DB's...? > > ----- Tibor Karaszi wrote: ----- > > The first thing you need to consider is whether the system databases are on the same path. If they are, then > SQL Server should start. If not, then SQL Server will not even start as it looks for model (which isn't in the > mast as stated in master..sysdatabases) and since model isn't there, it can't create tempdb and SQL Server > cannot live without tempdb. > > If the system databases are on the same path, all you need to do for your user database is to drop them (they > are suspect anyhow) and then try to attach to the database files using sp_attach_db. > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > > > "Cory" <Cory.ellingson@rcis.com> wrote in message news:0BD2AFC2-6EF6-4C7D-BC29-D99D37BE9FFE@microsoft.com... > > Hello, > >> I am trying to restore my databases to a new server for a BCP Drill, and I am running into a few issues. > >> When I try to restore the master (in single user mode -c -m), that appears to go well, however, when I try > to start SQL Server back up, it gives numerous error messages, stating the \\..\dbname.mdb and .log are not > there, when infact, they are not there. However, I am trying to restore. From what I can tell, restore the > master, then the user DB's...another possible kink is that the .mdb's and the .log's are on different drives > (F & G)... > >> Ideas? > >> Cory > > >
- Next message: Cory: "Re: Restore Master DB to New Server"
- Previous message: Tibor Karaszi: "Re: Limiting access to certain DB's"
- In reply to: Cory: "Re: Restore Master DB to New Server"
- Next in thread: Cory: "Re: Restore Master DB to New Server"
- Reply: Cory: "Re: Restore Master DB to New Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
