The title pretty much says it all - if you schedule a SQL Server job to run every X number of minutes, and it does not finish the previous call before the # of minutes is up, will it skip the run since it is already running, or will it run two instances of the job doing the same steps?
+7
A:
The SQL Server agent checks whether the job is already running before starting a new iteration. If you have long running job and its schedule comes up, it would be skipped until the next interval.
You can try this for yourself. If you try to start a job that's already running, you will get an error to that effect.
Jose Basilio
2009-05-14 19:11:36
Awesome, that's exactly what I wanted to know. I have an e-mail checker that sometimes takes a while to download large e-mails. Because it runs every minute, it's -very- important that a second instance of the job isn't started if the first one hasn't completed yet.
Daniel T.
2009-12-08 03:47:35
+1
A:
Which version of SQL Server are you using? This seems like a pretty easy thing to test. Set up a job with a WAITFOR in it that inserts a single row into a table and set up the job to run twice in quick succession (shorter than the WAITFOR DELAY).
When running such a test in SQL Server 2005 it skipped the run that was overlapped.
Tom H.
2009-05-14 19:15:21