Comments
Sort by recent activity
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...