Rebuilt master, what's next?

Hello,
What would be the way to go after rebuilding master database: (1)
restore it from the backup, restore msdb, and then user databases or (2)
restore user databases, restore master, and then msdb.
I mean, is it bad, when the master is restored w/o user databases being
accessible?
Many thanks,
Pablo
Hi,
What would be the way to go after rebuilding master database?
This is the correct step:- Restore it from the backup (Master) , Restore
msdb, and then user databases
Have a look into steps (15 - 28) in the attached link.
http://www.dbarecovery.com/restoremasterdb.html
I mean, is it bad, when the master is restored w/o user databases being
accessible?
You have to restore the Master database and then the user databases.
Otherwise Master database restore will
overwrite the existing database entries.
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hello,
> What would be the way to go after rebuilding master database: (1)
> restore it from the backup, restore msdb, and then user databases or (2)
> restore user databases, restore master, and then msdb.
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> --
> Many thanks,
> Pablo
|||Thanks, Hari.
Still, one thing remains unclear to me: what will happen when I restore
master then start the server and user databases aren't where they
supposed to be. Will the references to them in master be automatically
erased or will the databases be marked suspect? Will I have to drop the
suspect databases before restoring them or will I have to use WITH
REPLACE clause to force the restore over the existing (suspect) user
database?
Thanks,
Pablo
Hari wrote:
> Hi,
> What would be the way to go after rebuilding master database?
> This is the correct step:- Restore it from the backup (Master) , Restore
> msdb, and then user databases
> Have a look into steps (15 - 28) in the attached link.
> http://www.dbarecovery.com/restoremasterdb.html
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> You have to restore the Master database and then the user databases.
> Otherwise Master database restore will
> overwrite the existing database entries.
> Thanks
> Hari
> MCDBA
>
> "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
>
>
|||If SQL Server expects a databases's MDF file be in a place, and the file isn't there, you have a suspect
database. Drop it and do a regular restore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:uLaYNSvREHA.3628@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Thanks, Hari.
> Still, one thing remains unclear to me: what will happen when I restore
> master then start the server and user databases aren't where they
> supposed to be. Will the references to them in master be automatically
> erased or will the databases be marked suspect? Will I have to drop the
> suspect databases before restoring them or will I have to use WITH
> REPLACE clause to force the restore over the existing (suspect) user
> database?
> --
> Thanks,
> Pablo
> Hari wrote: