Last week we got discoverd that one of our SQL jobs was still running.
Nomally the job takes 5 minutes to run, but this time is was still running after 5 days.
The problem was due to the fact that the program that the SQL job was executing was "hung up" and did not respond.
The SQL job was however waiting for a reply.
Now, the server on which the SQL job was active is in SQL Monitor 3 and had the SQL Job Unusual and SQL job failed alerts activated.
However w didn't get an alert. Now since the job didn't report failure i can imagine the SQL Job failure doesn't do anything.
I did expect it from the SQL Job Unusual, since the time running was far higher than the normal time.
Can someone explain this?
Also, is there an option to create a custom metric for this?
Or perhaps another way to achive this?