Hi All,

I am looking for an approach to error branching.

I have a DTS package with 2 workflows. The primary
workflow performs the required task. The first step of the
second workflow, which acts as an error branch, has an
ActiveX workflow script which checks the status of all
steps for an error; if an error is found the step
executes, otherwise it retries. when it finds that the
last step is completed, it is set to DontExecute and
completes.

I find that this runs very slowly. If I disable the first
step in the error branch, the primary flow runs in 3
minutes. However, with that step enabled the package runs
in about 20 minutes!

I am looking for a better approach to error branching
where I wont have to put an error constraint on every
step. Any ideas?

Kind Regards,

Doug

In article <012201c3787f$6ae86260$a301280a (AT) phx (DOT) gbl>, Doug Holland
<dougholland (AT) hotmail (DOT) com> writes
Doug, I have yet to find one. Wouldn't it be nice to have Or logic on
workflow! Using a task with the retry step status is the only realistic
way to do this with a single task, but I too have found it hogs
resources.

Personally I use the logging to SQL server and the log files. I often
log additional information to the log to provide context information for
the current run. This can be done in ActiveX Script Tasks.

You could also do this kind of error checking from a calling
application, and if you have custom requirements this would probably be
the best way to go.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Hi Darren,

Thanks for your response. I get slightly better
performance if I drop the relative priority of the first
step of the error branch. I will have a look into your
suggestion.

Doug