Activity overview
Latest activity by emmar00
I have discovered that if the job is deleted, the alert will close. Disabling the job is not sufficient. (I assume this is based on viewable data in msdb that is no longer present after deleting the job.) I don't love it, but it does feel correct (there are no longer failed runs of job X). Plus, if the job isn't going to run again, does it really need to stay created out there? If not, maybe script it out and save it to disk or turn it into a more ad-hoc script (like a SQL Prompt snippet). / comments
I have discovered that if the job is deleted, the alert will close. Disabling the job is not sufficient. (I assume this is based on viewable data in msdb that is no longer present after deleting th...
New Forum Hate
I would just like to express how much I despise this forum UI.Why can't I make a new question from a forum page? I either have to back out to just Support > Community or click on a specific questio...
Closing alerts for failed jobs that won't run again
When I look at the “Job failure” alerts that have not Ended, I see there are quite a few “one off” jobs. Maybe these jobs were just from personal testing or maybe it was a one-time configuration jo...
Handling alerts that end in a suppression window
How should we handle alerts that are raised before a suppression window but end during one? For example, a CPU utilization alert (low priority but maybe worth looking at) is raised at 5:50 PM, our ...