Hi, I have package named "Refresh.dtsx" and this package is called in the job named End_End Refresh which has 5 steps. The package Refresh.dtsx is called at step 3. Due to some issue, am seeing that multiple instances of same package(Refresh.dtsx) running. Please let me know how to prevent multiple instances of a same package running. Thanks in advance. Regards, KiranSimple Living, High Thinking.. :)

Hi Kiran, Based on the description of the issue provided I have doubts that the same package gets executed in parallel with itself just from this step. Can you tell how did you arrive to the conclusion? Any evidence? Arthur My Blog

What I did once is include a task at the beginning of the package, that inserts the package name, the date and the string "Running" into a log table. At the end of the package, I would insert the same with "Finished in the table". Before this insert, I retrieve the maximum date of that log table for that package and check the string. If it is "running", stop the package (put an expression on a precedence constraint), if it is "finished" continue as usual.MCTS, MCITP - Please mark posts as answered where appropriate.

If you are running your package via a sql server agent job then the package cannot run in parallel cause the agent itself will not allow multiple threads of the job to be active at any given time.http://btsbee.wordpress.com/

What I did once is include a task at the beginning of the package, that inserts the package name, the date and the string "Running" into a log table. At the end of the package, I would insert the same with "Finished in the table". Before this insert, I retrieve the maximum date of that log table for that package and check the string. If it is "running", stop the package (put an expression on a precedence constraint), if it is "finished" continue as usual. MCTS, MCITP - Please mark posts as answered where appropriate. Just want to add one more thing in this... Add a SQL task on "On Error" event... that will update the record as "Failed". [otherwise, in case of failure your record will always be in Running state] Thanks Prasoon

I do the same thing as Koen, I just like to add that you can use sysSSISLog table as well if you have your SSIS logging set.Sincerely Nik -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

I suspect the issue is in the 1st run not being finished when a next job starts to run the same package again thus "multiple instances" of the same package occur. Happens when you have a schedule that is very tight. But I wanted to hear the whole story Arthur My Blog

I suspect the issue is in the 1st run not being finished when a next job starts to run the same package again thus "multiple instances" of the same package occur. Yes you are right, thats what i thinkSincerely Nik -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).