Without looking, name your most important server. Or if you have a bunch, name the top 2 or 3.
Now tell me what edition you are running. Not too hard. “SQL 2008 R2 Standard” or whatever.
Again, with out looking – what’s the build number? Hmmmm. 10.5…something or other.
Now imagine your server gets hit with a bad case of the Hulk Smash’s and it’s gone. Well good thing you have backups.
Now let’s just take our master database and restore that sucker right there on our backup machine. Uh-oh. What’s that error? 3168!?!?! NOO!!!
If you need to restore a master database (and let’s hope you don’t), you better know what build it is before you start down that path. What’s the best way to know all your build numbers for all your servers? Ugh…documentation. I know, I know. We all hate it but in this case it’s going to save you a headache.
Granted, you can get the build number from the error message above but do you really want to spend the time adding a service pack to your backup server before restoring your master DB? I’m sure the big boss man doesn’t want to have extra downtime.
I use a department wiki that has facts about all the production servers. Sometimes it’s a pain to keep updated but it’sÂ necessary.
Do you keep your build numbers documented?