Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



Anti-spam: How many eyes has a typical person?

Follow us on FB


SQL job scheduled run skipped due to long running job

AddThis Social Bookmark Button
If SQL agent finds a job running at schedule job start time, agent skips the execution of job until the next scheduled execution time. This can lead to some missing rows. I have tried to demonstrate the same thing below. Step-1 Create a Job with runs every two minutes and add below statement in job step just to simulate the real life scenario. waitfor delay '00:01:10' go Step-2 Set schedule to run every minute Leave job for few minutes. After that if we look at the job history, we can see that few executions of jobs are skipped. We have
scheduled it to run very minute but its getting run every two minutes. Step-3 Delete the job. Apparently this looks like a not a big deal. But if we are doing some data processing like populating the search table or sending data to third party application or may be running SSIS packages and this condition is not taken into consideration, it can be a data loss. Actually, today I find this as root cause for search not displaying some data in one proprietary system. Sometimes Job was running for more time due to blocking issues. Of course if proper tracking mechanism is...(Read whole news on source site)

Home : Blog List : Chintak's Blog : SQL job scheduled run skipped due to long running job