Re: master.mdf recovery
From: Anthony Thomas (ALThomas_at_kc.rr.com)
Date: 02/26/05
- Next message: danA: "Re: The remote server is not defined as a subscription server."
- Previous message: Anthony Thomas: "Re: Account to Run SQL under?"
- In reply to: Radis Bill: "master.mdf recovery"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 26 Feb 2005 12:48:20 -0600
>From the console, you might be able to start sqlservr with the -T3607
option. The recovers non of the databases, system nor users. This may
allow you to export the configuration contexts from the system tables from
within the master database. If you do this, then there is a chance that you
would have all the information necessary to replace the content on a rebuilt
master. However, THIS IS A COMPLICATED SITUATION. CALL MS PSS FOR
ASSISTANCE.
Sincerely,
Anthony Thomas
-- "Radis Bill" <Radis Bill@discussions.microsoft.com> wrote in message news:63EFB560-DFC7-4D36-B331-62846758B058@microsoft.com... Is it possible to recover master database from problematic master.mdf and/or problematic mastlog.ldf? No backups exist. The error that appeared in event log is Error:9003, Severity:20, State 1. and right after that: "Cannot recover master database.Exiting" . The reason I am posting this is that I know there is something starnge going on because there was no hard disk failure and the problem appeared after power loss of the server. But scan disk did not report any problem when the server rebooted after the power loss. So maybe the file is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.
- Next message: danA: "Re: The remote server is not defined as a subscription server."
- Previous message: Anthony Thomas: "Re: Account to Run SQL under?"
- In reply to: Radis Bill: "master.mdf recovery"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
