'Job did not start' alerts for 0 duration jobs

• 
  Hi Kevan,
  
  SQL Response will check to see that a scheduled job had run by examining its' "next run date" and "last run date" fields in the MSDB database. It should not discriminate against jobs that have no duration because it does not check that, except when checking for long-running jobs. There are other reasons why you may get a job not run alert:

  Possible causes:
  Previous execution of this job was overrunning
  SQL Server Agent was not running (a SQL Server Agent not running alert is raised when SQL Response first detects that SQL Server Agent is not running)
  No target servers defined

  
  Could it be one of these?

  Brian Donahue April 20, 2009 06:19

  - 0 +
• 
  Brian,
  
  thanks for the response. I have rechecked one of the alerts
  
  Previous execution of this job was overrunning - No - in fact the previous run had also finished with 0 duration, but that hadn't fired an alert
  
  SQL Server Agent was not running (a SQL Server Agent not running alert is raised when SQL Response first detects that SQL Server Agent is not running) - No - agent was certainly running
  
  No target servers defined - No, the target is set to 'local server'
  
  
  It is strange that other runs of the same job that have 0 duration are not triggering the alert - so I guess it isn't strictly a 0 duration issue. Could it be that SQL Response is doing a dirty read on the MSDB database?
  
  
  Kev

  kevriley April 20, 2009 07:02

  - 0 +
• 
  Hi Kev,
  
  We've had some issues in the past with false positives with the job did not run alert.
  
  What is the schedule of the job?
  
  Cheers,
  --
  Daniel

  dlkj April 20, 2009 11:58

  - 0 +
• 
  Daniel,
  
  schedule is "Occurs every day every 12 minute(s) between 00:10:00 and 23:40:00"
  
  Kev

  kevriley April 20, 2009 12:01

  - 0 +
• 
  Hi Kev,
  
  Does there seem to be any pattern to the false positives?
  
  I'm going to try and replicate the issue on a test machine.
  
  Cheers,
  --
  Daniel

  dlkj April 20, 2009 12:44

  - 0 +
• 
  Daniel,
  
  there seems to be no pattern. It is affecting different jobs at different times on different servers.
  
  Kev

  kevriley April 21, 2009 05:20

  - 0 +
• 
  Hi Kev,
  
  I've not had any joy reproducing the issue.
  
  What reason does SQL Response give for the job not running?
  Are the alert repository and the monitored server in the same time zone?

  dlkj April 21, 2009 09:10

  - 0 +
• 
  Daniel,
  
  Reason for not starting: Reasons unknown
  
  All servers are on the same timezone
  
  Kev

  kevriley April 21, 2009 10:32

  - 0 +
• 
  Hi Kev,
  
  Could you email me a copy of the job history and the details of some of the false positive alerts that you've seen so we can try to correlate the issue.
  
  Cheers,
  --
  Daniel

  dlkj April 23, 2009 06:43

  - 0 +
• 
  Daniel,
  
  will do. Should I use support@red-gate.com?
  
  How do you want the data? Job history I could export to Excel.
  Alerts - how do you want these?
  
  
  Kev

  kevriley April 23, 2009 06:48

  - 0 +
• 
  Hi Kev,
  
  yes, support@red-gate.com will be fine.
  
  Exported to excel or csv would be ideal.
  
  A few screen shots of the alerts and a list of the most recent occurrences would be great.
  
  Cheers,
  --
  Daniel

  dlkj April 23, 2009 07:42

  - 0 +
• 
  Daniel,
  
  have just emailed you.
  
  Kev

  kevriley April 23, 2009 09:50

  - 0 +
• 
  Just to close off this thread:
  
  We have managed to reproduce the problem and have logged it in our bug track system.
  
  Unfortunately we haven’t come up with a work around, but we are hoping to address this in an upcoming release.
  
  --
  Daniel

  dlkj May 05, 2009 09:07

  - 0 +

Add comment

Please sign in to leave a comment.