SSIS Scheduling Conflicts?
time to read 1 min | 50 words
I have two SSIS packages that cannot run concurrently, however, one must run once every 5 minutes, and the second every hour, so they are assured to conflict very soon. I can handle this situation manually, but I wanted to know if there was a builtin way to handle that.
Comments
Hmmm ... starting simply (and assuming your contending resource is a DB table):
BEGIN TRANSACTION
Matt,
I need to avoid doing a database - wide lock, which is what would happen when those monsters are running.
I also need to touch more than a single DB / resource, and a distributed transaction is not an option here.
Your situation warrants re-inventing distributed transactions, but not using them ?
/Mats
Mats,
Absolutely not!
I just need to ensure a serial execution of packages, nothing more. Transaction semantics are need to be more fine grained than a transaction per the entire package.
I wanted to know if there was a builtin way to provide the: "when package A runs, wait to run B, and vice versa"
Perhaps a better term is:
Do not run packages A,B,C in parallel
You can create a third package that runs those two packages in serial. For the one, you only want to run once a hour, you use some variable or if-statement,
Comment preview