May 15, 2011 at 9:41 pm
Comments posted to this topic are about the item A story of corrupted Master database in SQL Server 2008
May 16, 2011 at 1:35 am
Interesting story! You don't mention anything about what caused the corruption however?
One thing is fixing the corruption, but I'd be very wary of just restoring the system back the way it was, without examining what caused the corruption in the first place. If it's a fried IO subsystem, it's probably just a matter of time before the corruption reoccurs.
Mark S. Rasmussen
Blog: improve.dk
Twitter: @improvedk
Internals geek & author of OrcaMDF
May 16, 2011 at 2:03 am
Interesting read - thanks for sharing.
I'd be interested also in knowing the cause of the corruption.
Also, you say that you restored your user databases. I am assuming that they were also corrupt - possibly for the same unknown reason - although did you verify this? and if so, how?
some good tips there though - thanks.
May 16, 2011 at 2:27 am
I like Mark thinking and I would have followed Mark's point to know why such corrpution took place and to ensure it never happens again or if it does I have the solution to tackle it.
CEWalden
May 16, 2011 at 2:57 am
Thank-you for the article. It was a good read (sounded more like a blog post though). The readers got some good tips out of it, but what remains is a mystery is how the master database got corrupted. Something has to have gone wrong - things don't just blow up all of a sudden. It would have been nice if you could have made a passing reference (like "...the master database got corrupted because ... "). If it was something new or unheard of - it might save somebody else a few sleepless afternoons.
Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com
Follow me on
Twitter: @sqltwins
May 16, 2011 at 3:17 am
Good story! I think, you should as well add the link to the MSDN Library.
Rebuilding System Databases
http://msdn.microsoft.com/en-us/library/dd207003(v=SQL.100).aspx
Please tell us more about the reason of the corruption and why restoring user databases.
Greetings,
Christoph Muthmann
SQL Server MVP
Have a nice day,Christoph
May 16, 2011 at 3:22 am
How long did was your database now?
How do they fix WMI error?
Where you able to find any relationship between all the events (WMI, MOF, master corruption)?
Any clue about the root cause?
Regards Ramon
May 16, 2011 at 3:42 am
Just as a matter of curiosity, is there any reason why you didn't simply attach all the user databases? Had their original files disappeared?
May 16, 2011 at 4:43 am
Good article - I just have one tiny issue which I quote here: "We were lucky to have the backups of system and user databases available....:"
Having backups of your system and user databases should never (ever) be a matter of luck... Maybe you should put you Monday naps to better use and verify your backups:-P
May 16, 2011 at 6:30 am
After restoring master it is only necessary to attach the databases which were created after the last backup of master. All other databases should be available immediate.
Cheers,
Christoph
Have a nice day,Christoph
May 16, 2011 at 6:35 am
There was one step missing in your list. After:
4. Restored the latest backup of the master database.
There should be another restore:
4a. Restored the latest backup of the msdb database.
Kind regards,
Christoph
Have a nice day,Christoph
May 16, 2011 at 7:50 am
Good read, i have seen the WMI error previously but since it were inside a testing VM i just reverted the to prior snapshot, now i know how to fix it.
--
Thiago Dantas
@DantHimself
May 16, 2011 at 7:52 am
Good thing to share but it would be great if you shared the cause also so that many of us would be careful in future...
May 16, 2011 at 8:22 am
Can we just replace the master database and log files with a good backup, instead of running setup with rebuild option? I did that with SQL2005, would that work in sql2008 as well? and what would be the potential problems with just replacing mdf. and ldf files?
Thanks.
May 16, 2011 at 8:28 am
medicinformatics (5/16/2011)
Can we just replace the master database and log files with a good backup, instead of running setup with rebuild option? I did that with SQL2005, would that work in sql2008 as well? and what would be the potential problems with just replacing mdf. and ldf files?Thanks.
if you can fire sql server in single user with a corrupted master, then i guess you could, but i don't know if thats possible
--
Thiago Dantas
@DantHimself
Viewing 15 posts - 1 through 15 (of 35 total)
You must be logged in to reply to this topic. Login to reply