Thanks Mike. I, for example, have been mandated to set up an alert on the database that is raised when a particular user does any activity on the database. I thought SQL Monitor would help me there. Your thoughts folks?

In terms of the escalation, I feel that is something that could be built into the the tool relatively easily as opposed to requiring the customer to pay for a 3rd party service.

Thanks; that's useful to know.

With respect to being paged for High severity alerts, the PagerDuty integration that we've introduced in v2.3 may help. They can send SMS messages or call a phone, they handle schedules and escalation policies and they've added the ability to filter SQL Monitor alerts on severity. They're worth checking out.

I would also like to see the ability to have different notifications based on the alert threshold level. For example, I may want to get emailed for the LOW and MEDIUM levels, but maybe I need to be paged for the HIGH level.

Hi, David. Thanks for the quick response. Ideally, the more granular you can get with which alerts are checked against which instances, the better. In terms of your question regarding custom queries vs other counters, the more information that can be monitored, the better. My mind immediately goes to custom queries and possible adding more Perfmon Counters to check.

It's a great idea, and one we're likely to investigate in more detail.

A couple of quick questions -- would custom queries be sufficient, or would you also need the ability to, say, pull in other WMI counters? And would you need to control over which instances the custom queries were run against?