?I have a dts package which is run once per day and will fail on 1in6
attempts at execution with the above error. It is running on a dual proc
Win2000 Server, I have been unable to recreate it on a single proc dev
machine.

Is the issue related to the package stucture (we are using multiple strands
of execution coming from a single start point) ie should we be attempting to
reduce the amount of concurrency in the package (either running all steps
linear or by breaking half of the steps out into a subsequent package)

I haven't seen that error, but if you do want task to run in parallel then
need separate connections. Two tasks trying use the same SQL connection will
result in one being queued behind the other. Maybe in your case this queuing
is not working and the two clash, well that is what the error reads like
although I have never seen this happen myself, I just get queuing.

For preference I don't like to let stuff queue automatically, I'd rather use
workflow to ensure the order of execution, so it is clear to the package
designer/developer what will actually happen at run-time, or just ensure you
have one connection per concurrent task.


--
Darren Green
http://www.sqldts.com

"mrsifteruk" <mrsifteruk (AT) discussions (DOT) microsoft.com> wrote