Job Duration Unusual alert does not fire until job complete?

I discovered the hard way today that the Job Duration Unusual alert seems to only fire once the long-running job has completed or been manually stopped. Really??

This is an issue, and defeats a major purpose of the alert, namely that if a job hangs for any reason, I need to know about that and intervene.

Can this be fixed?

MckMurray November 28, 2016 09:48

Comments

4 comments

Hi MckMurray,

Thanks for posting on the Redgate forums.

There is an open bug request for this with internal reference SRP-10912. I will update this forum post further when I get any news on this.

Dan B November 29, 2016 10:28

0
Would really love to see this fixed. Catching a "hung" job is our principal objective with this alert as well.

awalther_golf July 05, 2017 15:36

0
Do you have any update for this topic?

rre November 08, 2018 15:19

0
I came across this thread in a search, so it's a little overdue but no this hasn't been implemented yet. Just to clarify this isn't a bug, but an enhancement request: https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/33919051-job-duration-taking-too-long-triggering-while-jo.

Russell D May 10, 2019 07:33

0

Add comment

Please sign in to leave a comment.

How can we help you today?

Job Duration Unusual alert does not fire until job complete?

Comments

Add comment