March 14, 2007 at 2:43 pm
Hello,
I've created a DTS package that runs well. I've created a job to run the package. However, I need this package to run pretty much all day to catch us up with our backlog of data to process.
I was going to schedule the job for every ten minutes. My thought was that even it the previous run wasn't finished, it would stay queued until it could run.
Most of the time the package take 2 minutes to run. It has taken 25 minutes during a peak time of the day.
Question: Is this a good idea? Will the package run consecutively? Will it run concurrently, if the previous run hasn't finished? Is there a way to insure that the package runs consecutively?
I need to the package to finish processing one batch of data before beginning the next batch.
Thanks for your help!
Tony
Things will work out. Get back up, change some parameters and recode.
March 15, 2007 at 8:54 am
Tony,
Only one instance of a job can be run at a time, so if it's still running when the next run is scheduled, SQL Server Agent will not start it.
As an example, say the job scheduled to run every ten minutes starts at 10:00 and runs for 25 minutes. The 10:10 and 10:20 runs won't be started, but the 10:30 run will be.
Greg
Greg
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply