Always mention the particular data object (stored procedure) causing the alert
Right now we get a lot of "long running querys" without the alert screen or the email mentioning what data object is causing this. When checking details the data is there (in the form of a "create procedure"), so it can't be too hard to extract this information!
This is important for two reasons:
1 (Most important) You want to have customized alert options for certain data objects! For example, we don't want alerts when a backup, index rebuild or a long running SP is running. We need a longer timeout for these alerts.
This can now be acciomplished with the global regexp exclude on particular querys on the whole database, but it doesn't work correctly and reg exps are hard and fragile.
2. When you get an email, you always want to know what is causing this
Hi all, we are hoping to get this into place within the next one or two releases of SQL Monitor (finally).
ADAM, It has been almost a YEAR since your post. Any UPDATES?
Would that you could improve the Alert's "SQL Culprit". I have a UDF that is heavily used, so the snippet I see is that code, not the underlying code that used it, so I'm utterly blind and the Alert is nigh on useless. Is there ANYTHING you can do to "give me more about the context", please?
I think this falls in with this request. Alerts on SQL Agent Jobs should include the job name, not jus the HEX ID. How hard could it be to run :
SELECT name FROM msdb.dbo.sysjobs_view WHERE job_id =
CAST(@JobIDVariable AS UNIQUEIDENTIFIER)
Simon, thanks for your feedback and sincere apologies that we missed this feedback at the time - clearly it is a popular suggestion!
We have now logged this and are tracking it and I'll post here when we have any updates...