Ayende @ Rahien

Refunds available at head office

SSIS Scheduling Conflicts?

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

Matt
06/27/2007 03:46 PM by
Matt

Hmmm ... starting simply (and assuming your contending resource is a DB table):

BEGIN TRANSACTION

Ayende Rahien
06/27/2007 04:47 PM by
Ayende Rahien

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.

Mats Helander
06/27/2007 06:56 PM by
Mats Helander

Your situation warrants re-inventing distributed transactions, but not using them ?

/Mats

Ayende Rahien
06/27/2007 07:01 PM by
Ayende Rahien

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"

Ayende Rahien
06/27/2007 07:01 PM by
Ayende Rahien

Perhaps a better term is:

Do not run packages A,B,C in parallel

Rémy
06/28/2007 09:14 PM by
Rémy

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,

Comments have been closed on this topic.