|
If I have a job in SQL Server 2005/2008, and it is scheduled to run every minute, what happens if one of the executions takes 75 seconds? Does the agent miss an execution or do I have two copies executing simultaneously?
(comments are locked)
|
|
SQL Server will only run one instance of a job at a time. When a job runs past its next scheduled start time, that execution is skipped and the job picks up again at its regularly scheduled time. Ken, have you ever, per chance, ever appeared on a popular TV trivia game show?
Feb 14 '10 at 04:29 PM
Scot Hauder
Not to my knowledge. If you've seen me on one, please let me know.
Feb 16 '10 at 01:04 AM
KenJ
I knew Ken Jennings was in IT before appearing on Jeopardy, he once drew a face on the monitor similar to your avatar but he is from UT not NE..so I thought I'd maybe there was a chance...
Feb 16 '10 at 10:25 PM
Scot Hauder
(comments are locked)
|
|
When scheduling a job, you indicate a start date/time and then a recurrence frequency. If it is scheduled to run every minute, it will attempt to run at the beginning of each minute, but only if it is not already running. If it is running, it will start again at the beginning of the next minute after it stops.
(comments are locked)
|
|
The next execution would be skipped.
(comments are locked)
|
