February 17, 2010 at 12:23 pm
If it is a crisis and the databases are down, it serves nobody to finger-point. Server Team, Admin Team, SAN Team, and Database Team (occasionally development team) had better all be on the same page to resolve the issue. It isn't a matter of who did their job or not. Something happened and it needs fixed. If you have an outage wrap-up meeting afterward, then discuss concerns there, discuss issues there, and do it without fingerpointing.
It is a fact that sometimes one group will find something before another - it happens. Everybody is typically looking for different things and sometimes alerts might overlap. No matter who catches the problem, it is up to all teams with a stake in keeping the systems up to get it FIXED TOGETHER.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 17, 2010 at 12:29 pm
CirquedeSQLeil (2/17/2010)
If it is a crisis and the databases are down, it serves nobody to finger-point. Server Team, Admin Team, SAN Team, and Database Team (occasionally development team) had better all be on the same page to resolve the issue. It isn't a matter of who did their job or not. Something happened and it needs fixed. If you have an outage wrap-up meeting afterward, then discuss concerns there, discuss issues there, and do it without fingerpointing.It is a fact that sometimes one group will find something before another - it happens. Everybody is typically looking for different things and sometimes alerts might overlap. No matter who catches the problem, it is up to all teams with a stake in keeping the systems up to get it FIXED TOGETHER.
Well said and agreed with!
February 17, 2010 at 12:57 pm
GSquared (2/17/2010)
Elliott W
You get a call, there is something wrong with database X, nobody else told you anything, you don't have any other information.
Ideally, you should have something that monitors the databases for you. A select from sys.databases where the state is in 4 or 5 should cause an alert to be sent to you if it finds anything. Won't work every time, but it is a good thing to have.
Agreed, that would be best, but even that will not run every second, and users tend to call when things go south.. So if you run that process every 3-5 minutes it is just as likely that you will get a call.. But your point is still valid.
CEWII
Viewing 3 posts - 61 through 62 (of 62 total)
You must be logged in to reply to this topic. Login to reply