SQL agent job didn't run as scheduled time

Question

SQL agent job didn't run as scheduled time

jpmathew10

Old Hand

Points: 342
More actions
July 28, 2011 at 12:26 am

#245046

I have created and scheduled the job in SQL server 2008 R2 SP1 server.
But i found that the job is not run as per the schedule.It often run after 5/6 hours delay.
What could be the reason. Pls advice

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 1

You may want to post additional information so that someone can better assist you.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

chandan_jha18 SSChampion Points: 11330 More actions · Answer 2

jpmathew10 (7/28/2011)
I have created and scheduled the job in SQL server 2008 R2 SP1 server.
But i found that the job is not run as per the schedule.It often run after 5/6 hours delay.
What could be the reason. Pls advice

One of the reasons that I can see is that if one of your schedules exceed its time limit,the next one may get skipped.

For example. Lets say you run this job every hour starting from 2 pm. So the next schedule is at 3 pm .If the job which started at 2 pm kept executing till 3:30 pm, then the 3pm schedule got skipped and it will run again at 4 pm. If the job at 2 pm got finsihed at 4:05 pm, it will mean that it skipped 3pm and 4pm schedules and will run at 5 pm now.

Check the job history about its execution times and see if it overlapped your scheudles. also, do check SQL logs on those times.

Chandan

jpmathew10 Old Hand Points: 342 More actions · Answer 3

Thanks for the reply!!

The job scheduled daily @ 3:00AM.It took around 5 min to complete.The next scheduled time, can we see in job is 3:00AM next day.

But the job will executes @ different time 5 or 6 hour after the schedule

jpmathew10 Old Hand Points: 342 More actions · Answer 4

The job scheduled daily @ 3:00AM.And it took below 10 mins to complete.

But the job executed daily @ different times

Like 9:45AM,8:57AM,9:05AM,10:30AM,9:33AM etc

Shark Energy SSCrazy Eights Points: 8389 More actions · Answer 5

Did anyone else set up some SQL Jobs that may be calling this task at different times?

We had a job on our server that seemed to be logging every 2 hours but was only scheduled once a day, turned out an old legacy job was calling it as its final step.

chandan_jha18 SSChampion Points: 11330 More actions · Answer 6

jpmathew10 (7/28/2011)
The job scheduled daily @ 3:00AM.And it took below 10 mins to complete.
But the job executed daily @ different times
Like 9:45AM,8:57AM,9:05AM,10:30AM,9:33AM etc

then surely there is something else causing these jobs to fire. You may want to use a profiler trace with appropriate filters to see what is causing this behavior.

Brandie Tarvin SSC Guru Points: 173068 More actions · Answer 7

I agree with the others. Something else is calling this job or starting it.

Check msdb.dbo.sysjobs joined to msdb.dbo.sysjobsteps to find any job steps that use the sp_start_job proc or call the job_id of this job.

If there's nothing there, then someone might be calling the job manually. A server side trace or Profiler might be able to catch the user name who set it off. (key word being "might").

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.