Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««1234

Rebuild SQL Server Master Databases in Less than 5 Minutes Expand / Collapse
Author
Message
Posted Monday, March 7, 2011 11:34 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, July 14, 2014 10:52 PM
Points: 58, Visits: 239
Ah, so he did. Clever fellow. I will edit the post to remove the "please credit me" comments.
Post #1074340
Posted Monday, March 7, 2011 11:38 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, July 18, 2014 12:37 PM
Points: 312, Visits: 1,098
Just goes to show how there are many ways to get the same job done.

Thanks for your comments,

Rudy



Post #1074344
Posted Thursday, August 18, 2011 11:23 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 24, 2014 12:05 PM
Points: 9, Visits: 241
This tip/how-to assumes that you can connect to the SQL Server instance. If I lost the master database, being able to connect would be the first thing I would worry about. Maybe you mean that if I move the copies I made before the accident back to replace the damaged master files, then I could connect. I have not had that experience yet. In any case, this looks like a good, solid tip.

Thank You,
David Shink
Post #1161948
Posted Thursday, August 18, 2011 11:36 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, July 14, 2014 10:52 PM
Points: 58, Visits: 239
Yes, but do a copy action not a move action, to ensure the destination folder's security settings are applied to the files. The DBA team I am part of has been relying on the method I described for two years of DR exercises and it has always worked. Our daily backup generates fresh copies of the System Database files every day (as soon as the backups are created, we via restore each to a different db name and file location then detach the new db).

For a recovery, we no longer restore the System Dbs from backups - we just copy the most recent copies of the files back into the original location(s) and then start up the engine. The only catch we have encountered is that you have to take ownership of the detached files and grant yourself access to them before you can copy them (upon detach, SQL Server reduces the rights to the MDF and LDF files so that only the identify that detached them has any access).

Post #1161952
Posted Thursday, August 18, 2011 11:51 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 24, 2014 12:05 PM
Points: 9, Visits: 241
Larry:

I am somewhat of a newbie to SQL Server database administration. Your last post is just the sort of thing I would need if I really lost the master database, and users, and my manager were standing over me asking when it will be "fixed". I guess we have all been there. Thank you for taking the time.

David Shink
Post #1161963
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse