http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660You 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, http://ayende.com/2600/ssis-scheduling-conflicts#comment6http://ayende.com/2600/ssis-scheduling-conflicts#comment6Thu, 28 Jun 2007 21:14:45 GMTPerhaps a better term is: Do not run packages A,B,C in parallel http://ayende.com/2600/ssis-scheduling-conflicts#comment5http://ayende.com/2600/ssis-scheduling-conflicts#comment5Wed, 27 Jun 2007 19:01:24 GMTMats, 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" http://ayende.com/2600/ssis-scheduling-conflicts#comment4http://ayende.com/2600/ssis-scheduling-conflicts#comment4Wed, 27 Jun 2007 19:01:01 GMTYour situation warrants re-inventing distributed transactions, but not using them ? /Mats http://ayende.com/2600/ssis-scheduling-conflicts#comment3http://ayende.com/2600/ssis-scheduling-conflicts#comment3Wed, 27 Jun 2007 18:56:25 GMTMatt, 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. http://ayende.com/2600/ssis-scheduling-conflicts#comment2http://ayende.com/2600/ssis-scheduling-conflicts#comment2Wed, 27 Jun 2007 16:47:08 GMTHmmm ... starting simply (and assuming your contending resource is a DB table): BEGIN TRANSACTION http://ayende.com/2600/ssis-scheduling-conflicts#comment1http://ayende.com/2600/ssis-scheduling-conflicts#comment1Wed, 27 Jun 2007 15:46:00 GMT