Re: corrupt master DB

From: Hari (hari_prasad_k_at_hotmail.com)
Date: 04/30/04 

Date: Fri, 30 Apr 2004 08:57:36 +0530

Hi,

Go thru the below article, this gives you the step by step GUI process to
rebuild the master database using rebuildm.exe. This will also detail the
steps
to restore the old backup.

http://www.dbarecovery.com/restoremasterdb.html

Thanks
Hari
MCDBA

"Susan White" <swhite@lifetouch.com> wrote in message
news:642901c42e2f$baef1db0$a101280a@phx.gbl...
> We had disk failures and SQL Server won't come back up
> because the master DB is corrupt. Is there any recovery
> method other than re-installing SQL Server nad then
> recovering the application databases

Relevant Pages

  • Re: Scripting in Windows 2000 Advanced Server
    ... "mssqlserver service which is clustered". ... used them in a script to determine if a service is running. ... to attempt to connect to the master database in the default instance of SQL ... ' Cannot start SQL Server - ignore error. ...
    (microsoft.public.windows.server.scripting)
  • Re: Scripting in Windows 2000 Advanced Server
    ... "mssqlserver service which is clustered". ... to attempt to connect to the master database in the default instance of SQL ... ' Cannot start SQL Server - ignore error. ... ' Connection string for SQL Server Master database ...
    (microsoft.public.windows.server.scripting)
  • Re: unable to start SQL Service ... error code 3417
    ... If the Master database is corrupt, how would you advise I maybe replace with ... "SQL Server cannot start the master database. ... MVP - Windows Live Platform ...
    (microsoft.public.sqlserver.server)
  • RE: master DB users
    ... (No user other than DBA should be allowed to access the master database). ... explicitly to database users in master, except those that SQL Server ... Those that are not in the sys schema ...
    (microsoft.public.sqlserver.security)
  • Re: Cluster will not fail over.
    ... Could not recover the master database! ... If you intend to stay on SP3 (for SQL Server), you should at least apply the ... >> From SQL server logs ...
    (microsoft.public.sqlserver.clustering)