October 18, 2011 at 10:35 am
In the event of disaster where there is no master database backup ( i always back up my system databases by the way). Why not just uninstall and re-install SQL instead, rather than rebuilding the master?
October 18, 2011 at 10:52 am
I will turn the question around.. Think about what is stored in master, all the logins and references to all the databases. Now the database references are usually pretty easy to track down, if we are smart they are in a limited number of places. As for logins if you have more than a couple this can be quite a challenge especially considering that the way security is handled. When a useris created in a database it references the SID of the login stored in master. You can drop and recreate a user with exactly the same name but the SID will be different and that means that the database will no longer know that the user should be allowed access to it or what permissions it should have. We also lose linked servers, auditing, and all configuration. While all can be rebuilt it is a pain.
Base position I strive to NEVER be in a position that I can't get master back from a backup. Even if that backup is 3-4 weeks old, its still better than a rebuild for me.
CEWII
October 18, 2011 at 10:59 am
MarvinTheAndriod (10/18/2011)
Why not just uninstall and re-install SQL instead, rather than rebuilding the master?
Because it takes longer.
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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply