How can we help you today? How can we help you today?

Job did not start ( overrunning)

This may apply to other Job did not start incidents but for this one here is my wishlist ( in no particular order):
1. Display the whole job description by wrapping the text
2. Show when the job was scheduled to start
3. Show how long the current run has been running for, or when the current run started.
4. You have a restart job button. It would be nice to just be able to cancel/stop the job as well. Sometimes I stop it and don't always start it again right then and there.[/list]
Giggles220
0

Comments

3 comments

Sort by
  • priyasinha
    Hi,

    Thanks a lot for the feedback. We have included all this in our requested feature list and we will try our best to accommodate as many features as possible in the final release. But in the mean while please do keep posting features which you would like to see in the final release of SQL Response.

    Thanks a lot.

    Regards,
    Priya
    priyasinha
    0
  • PDinCA
    I'm assuming that the erroneous posting of this Incident is also being addressed for the final release? In my case, the job ran successfully for 48 seconds, emitting complete step-history information that SSMS Job Monitor happily displays... The Job execution in question is picked up by the "Long running query" Incident detector - perhaps they are confusing each other...?

    SS2K 8.00.2039
    PDinCA
    0
  • Nigel Morse
    This particular incident is meant to occur when a job didn't start beacuse the previous run of the job is still executing. SQL Agent won't start a job untill the previous run has finished - but nothing will show in the job history about that.

    However as the job only runs for 48 seconds, unless you're scheduling it to run more often than that then you shouldn't be seeing it.

    Could you perhaps send us some screenshots of the incidents and corresponding times from the job monitor again please?

    Thanks
    Nigel Morse
    0

Add comment

Please sign in to leave a comment.