This morning one of our VMWare clusters went down when our SAN guys inadvertently unplugged the wrong storage array. Oops! We had to reboot some of our development and test servers including my SQL Servers. No big deal, this happens from time to time.
Good manners dictate that I notify the effected application administrators so they don’t panic seeing their connections drop. This is a pretty normal procedure. In my previous positions I had at the most five servers and I knew every database and who it belonged to. However, in this environment, I have almost 300 databases and knowing what they go to and who to contact is handled by a spreadsheet that was created before I started. Seems like there should be a better way to track this and to notify me when new databases are created. How are you handling this task?
Posted on July 23, 2012, in Maintenance, Monitoring. Bookmark the permalink. 1 Comment.
Typically locate the previous email I sent out about that server (facepalm).