all groups > sql server dts > october 2007 >
You're in the

sql server dts

group:

Running two Steps at the same time


Running two Steps at the same time Chris
10/11/2007 8:36:00 PM
sql server dts:
Is there a way to run two DTS steps at the same time? I need to speed a job
up that kicks off a DTS package and in the DTS package there are many steps.
None of them rely on each other to finish, except for one at the very end,
but I can speed it up if I branch off a few steps to run at the same time.

Is this possible?

Thanks for your help

-Chris
Re: Running two Steps at the same time Dan Guzman
10/13/2007 12:00:00 AM
Multiple steps can run concurrently as long as:

1) steps are not constrained by workflow precedence with the package

2) package properties specify max parallel tasks > 1 (default is 4)

3) the package is run from a multi-threaded app like DTSRUN or Enterprise
Manager

Note that multiple steps can be dependent on the same predecessor and
subsequent steps are free to run once the predecessor completes. For
example, you can load a staging table and then run multiple Execute SQL
tasks in parallel after the load successfully completes.

--
Hope this helps.

Dan Guzman
SQL Server MVP

[quoted text, click to view]
Re: Running two Steps at the same time Chris
10/13/2007 1:12:01 PM
Great Thanks Dan,

-Chris


[quoted text, click to view]
Re: Running two Steps at the same time Chris
10/16/2007 5:32:02 AM
I have the branches installed now and the max parallel tasks set at 15 just
in case. But for some reason after about 9 or 10 steps it reverts back to
running only one step. It trades off the after each step back and forth until
it is complete. Very strange. It starts off fine running the branches at the
same time so I know part of it is working but for some reason it always
reverts back to running only one step at a time.

Is there a reason for this?

Again thanks for your help

[quoted text, click to view]
Re: Running two Steps at the same time Dan Guzman
10/16/2007 8:08:18 PM
[quoted text, click to view]

I'm not sure what might be going on here but perhaps these processes are
resource intensive so only one can run at a time.

--
Hope this helps.

Dan Guzman
SQL Server MVP

[quoted text, click to view]
AddThis Social Bookmark Button