April 7, 2011 at 5:47 pm
Hi everybody !
What happens if ...
1) Master.mdf from server A (sql2005) becomes corrupt and sql A won's start. There is no backup except those belongings of the production tables
This master.mdf contais a lot of users, views an sp, so many info that we can't describe. So rebuilding is not an option.
2) Rename master and mastlog to XMaster and Xmastlog from server A
3) Create a database XMaster and Xmastlog on server B.
4) Stop SQL B and replace the files XMaster and Xmastlog with the corrupted versions.
5) Start server B
6) run dbcc checkdb on xmaster
7) Stop server B.
8) Copy repaired XMaster and Xmastlog to server A
9) Rename the files to master and mastlog
10) Start Server A
so... You are the experts!
Will sql A have a chance of start? or this is completely maddness???
Of course is one of you have a working utility like Stellar SQL recovery or Systools SQL Recovery or something like that and want to share it with me, I would be very very happy!
Sincerely: estebandelatorre@hotmail.com
and thanks for your time
April 7, 2011 at 9:14 pm
You could try attaching copies of the master DB on Server B, but it is very unlikely to work.
You can rebuild the master database, but you would loose anything you have built in it. (You really shouldn't have much other than users in the master DB, and you might just have to re-create all of them.)
April 7, 2011 at 9:14 pm
First: I would take your email address out of the post. If you need someone to email you they can do so through SSC forum tools, it will send it to whatever email you registered with. AND why are there no backups?
Second: I'm not completely sure your plan will work. I believe the issue you will have is if the two instances are not the same version of SQL Server. Once you attach the database to ServerB it will be tied to that version. (I think.) Though before attaching it to server B, make a copy of the MDF and LDF files (just in case).
If it does not work then your only option is to rebuild it. If you can attach the corrupted master database from ServerA to ServerB and repair it, you should be able to pull out the objects you need to rebuild them on a fresh Server A master database.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 8, 2011 at 12:23 am
Madness.
Repairing master (even a copied master) is unlikely to work. Most of master are system objects (all of master should be) and if there's something wrong severe enough to prevent SQL from starting, it's going to be severe.
What's the errors anyway?
Alternative that might work.
1) Take copies of the corrupt master.mdf and master.ldf
2) Attach them to another server as a user database
3) Extract all the objects from there (script them)
4) Rebuild the corrupt master on Server A
5) Apply all the scripts.
6) Fix your backup strategy.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 5, 2011 at 11:26 pm
This was removed by the editor as SPAM
May 6, 2011 at 8:31 am
Madness.
Repairing master (even a copied master) is unlikely to work. Most of master are system objects (all of master should be) and if there's something wrong severe enough to prevent SQL from starting, it's going to be severe.
What's the errors anyway?
Alternative that might work.
1) Take copies of the corrupt master.mdf and master.ldf
2) Attach them to another server as a user database
3) Extract all the objects from there (script them)
4) Rebuild the corrupt master on Server A
5) Apply all the scripts.
6) Fix your backup strategy.
Agreed
plan your system databases backup also
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
May 20, 2011 at 6:21 am
This was removed by the editor as SPAM
January 6, 2016 at 8:56 am
Every so often when we have an outage OR I apply a CU or Service Pack I will shutdown sql server and file copy master and model to another folder directory. SO... just in case something goes boom and master or model get corrupted I can get SQL Server backup up and running with those, then restore master and/or model from a daily backup to get it up to current.
January 6, 2016 at 11:10 pm
Hi everybody !
What happens if ...
1) Master.mdf from server A (sql2005) becomes corrupt and sql A won's start. There is no backup except those belongings of the production tables
This master.mdf contais a lot of users, views an sp, so many info that we can't describe. So rebuilding is not an option.
2) Rename master and mastlog to XMaster and Xmastlog from server A
3) Create a database XMaster and Xmastlog on server B.
4) Stop SQL B and replace the files XMaster and Xmastlog with the corrupted versions.
5) Start server B
6) run dbcc checkdb on xmaster
7) Stop server B.
8) Copy repaired XMaster and Xmastlog to server A
9) Rename the files to master and mastlog
10) Start Server A
Will sql A have a chance of start? or this is completely maddness???
You can recover master.mdf by using the inbuilt rebuildm tool, which is located at. .\tools\binn directory (C: . . .\tools\binn> rebuildm.exe. This can help us to recover the corrupted master database.
Of course is one of you have a working utility like Stellar SQL recovery or Systools SQL Recovery or something like that and want to share it with me, I would be very very happy!
Download the demo version of both software and check the following points:
1.) Are they both able to recover MDF Files?
2.) Compare and find out which software possess more features.
3.) Check which software is much costly or cheaper and if any of them is, then find out the selected brand comprises with any feature that can put impact on data restoration.
Note: I have analyzed both of them personally and found both identical, but when it comes to price, then SysTools’s software does cost low in comparison of Stellar.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply