Task Execution Order in Pkg w/o Workflow

[thermidor]

Hi All,

I have inherited a DTS package, without documentation, that has several tasks that are not explicitly connected by workflow. Is there any way I can determine the order in which the steps run without actually running the package?

TIA,
Sven

 

[dbomrrsm]

not sure but if the package has been run before and a package log created then you may get some info in there.

[blue]DBomrrsm[/blue]

 

[EdwinGene]

If the package has run correctly in the past, check the Workflow properties of the 'floating' tasks (right-click the Icon, select 'Workflow' then 'Workflow Properties'). On the 'Options' tab, in the 'Execution' frame there is a checkbox with the label 'Disable this step'. If the DTS package is running correctly, all but one of the 'floating' tasks should show as disabled, and the one that is not disabled will be the starting task for the package. If more than one of the 'floating' tasks does not show disabled, then any of those tasks could kick off at any time giving you unpredictable results.

I tried using 'floating' tasks at one time in order to have reusable, non-redundant functions in my DTS package (such as writing to an error log), but I decided I couldn't 100% count on the floating tasks being disabled when the package started, if anything had gone wrong during the previous execution of the package, so I abandoned it.