January 18, 2010 at 3:00 am
Hi there
I have been tasked with coming up with a minimum dataset for alerting in regards to severity, logins, performance counters etc
This is obviously a massive area for coming up with an alerting strategy and was wondering if anyone could point to any existing alerting strategies or advise on what I should include in a minimum dataset for this in regards to SQL 2005.
Thanks for any help
January 19, 2010 at 5:57 am
I monitor:
hanging spids\agent jobs
failed jobs
hypothetical indexes
disk space
deadlocks
January 19, 2010 at 6:03 am
hanging spids\agent jobs
failed jobs
hypothetical indexes
disk space
deadlocks
might want to add:
High CPU, Memory and disk utilization....log percentage used....
Change in DB Status (Online -> offline/Single_User etc..)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
January 19, 2010 at 7:38 am
Alerts for services
failed logins
Connectivity issues
tempdb growth etc...
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 19, 2010 at 9:59 am
Off the top of my head, I monitor:
Blocking above a time threshold
hanging spids
failed jobs
disk space
File sizes/free space
deadlocks
best practice (i.e. indexes created on correct filegroup, etc)
SQL guy and Houston Magician
January 20, 2010 at 9:43 am
Hi all - thanks for the replies it has given me something to start with. What about alerting on severity errors also I take it thats worth tracking?
January 21, 2010 at 3:14 pm
I typically alert on severities 17 and higher as those are considered critical.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply