Peter Schott (6/19/2013)
I'm blessed to work with another DBA who subscribes to the ideas behind the "lazy DBA" philosophy - don't work harder/more than you have to. He set up some phenomenal monitoring and alerting around all of our scheduled jobs. If a new job is created, it will soon be modified to send alerts on failure. Those alerts pull out the relevant details about any failures that occurred and send those along with the alert. We have alerts for drives out of space that contain a brief listing of critical DB files on those drives. We get detailed failure notices for replication if it has issues. We even have visibility into basic stats/items running on our servers over a web interface for when it's needed.
I agree with Steve's point that this is one of many areas that could be enhanced. Andy also makes a good point that MS could just buy/tweak an existing solution without too much trouble.
Of course, having read this I think I need to bug my co-worker about putting some of this info in a blog post. It would be really helpful to people who manage quite a few systems.
Einstein once said: If you can't explain a subject in simple terms to a layman, you don't know enough about the subject yourself.
Your DBA has mastered that concept and is the DBA every company "should" have. But then, I am sure he keeps himself abreast of developments, makes sure those less skilled have the answers to questions they need in a manner they can understand and realises the importantance of continuation training. That guy deserves that pat on the back but then companies that have that sort of professionalism take it for granted and reason that "he is only doing the job he is paid for".
Easy to use software, less complex practices, the ability to say "well, it isn't my job anyway": What ever happened to good old-fashioned workplace-pride and standards where the individual knew what needed to be done and simply did it?
(Disclaimer: Not in a good mood this morning and feeling very cynical....)