More than likely, you are going to have to store this in your DB and then
write some really good ActiveX script(s) to disable all tasks in Package 2
that you don't want to run. As for the parent package, all you need is a
count like 2 to indicate to start with package 2 (used by yet another
ActiveX script). It also depends on your workflow on how you would do this.
If you have loops or complex workflows, this will become that much more
difficult. My advice is to reprogram it so that even if a failure occurs,
you can still rerun the whole thing without adverse effects (e.g.
delete/move files after import so that if a later task fails the file
doesn't reimport and mess you up). That will save you alot of headaches in
the future. Not sure what you are doing, but that will be your best bet
with the least amount of coding overall and the lest likelihood of bugs.
Most of the time, a simple solution like the delete/move file, adding a
temporary table or status column into the mix makes it so that you can run
from the beginning without adversely effecting your production environment
or leaving something half-baked. Everything not done will wait for the next
run to resume. Just have your tasks in the packages only touch the records
at that stage of processing.
AFAIK, there is no automatic RESUME function in DTS.
Scott
"GS" <GS (AT) discussions (DOT) microsoft.com> wrote
Quote:
I have a parent package which i am scheduling to run every month. The
parent
package has 6 child packages and they inturn have many steps.
Assume Task 3 or package 2 fails. The support person will rectify the
error
and he will re-run the package. Now when he re-runs I want the package to
start from Task3 of package 2 and not from the beginning. How will I
enable
all the tasks before Task3 to skip.
Thanks
Gomathi Sarma |