Package Synchronization?

What is the best strategy for maintaining package execution synchronization when using the SSIS API?

For example, I have discovered that it is quite possible to fire off several intances of the same package simultaneously.

Is a best practice perhaps to put the db in single user mode prior to kicking off the package and if so, how would you limit subsequent ASP.NET connectons, for example?

TIA,

Rick

Assert.True wrote:

What is the best strategy for maintaining package execution synchronization when using the SSIS API?

For example, I have discovered that it is quite possible to fire off several intances of the same package simultaneously.

Is a best practice perhaps to put the db in single user mode prior to kicking off the package and if so, how would you limit subsequent ASP.NET connectons, for example?

TIA,

Rick

Control access to the package so that it DOESN'T get fired simultaneously.

-Jamie

|||You can create Agent Job with your package. The Agent ensures only one instance of a particular Job is executed at the same time. Of course, it will be your responsibility to make sure the package is only executed via Agent (from ASP.NET - use sp_start_job SQL stored proc).