DTS Packages (Adding failure checks)

Question

Post reply

DTS Packages (Adding failure checks)

jo Mong

Say Hey Kid

Points: 698
More actions
January 6, 2005 at 8:47 am

#60588

How comes DTS does not exucute failure packages added to already existing package (execpt adding them at the very end)? I checked the sequence of execution after adding the failure part and it was last in the list (though physically it is not).

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Nicholas Cain SSC-Dedicated Points: 33009 More actions · Answer 1

It's last in the list, however that's not the execution order.

It adds components to the list in the order which they were added to the package.

Shamless self promotion - read my blog http://sirsql.net

jo Mong Say Hey Kid Points: 698 More actions · Answer 2

Thanks Nicholas.

Is there a way one can add ON FAILURE sub-packages on already existing package and have then Execute when they are supposed to. I tried and mine did not Execute when they were suppposed because they placed down the list.

Nicholas Cain SSC-Dedicated Points: 33009 More actions · Answer 3

On failure will execute in the event of a failure, do you have the ON FAILURE workflow going towards the package?

Be careful not to have multiple on failure workflows to the package, create a copy of the package for each step you want to execute the package for in an on failure workflow

Shamless self promotion - read my blog http://sirsql.net

jo Mong Say Hey Kid Points: 698 More actions · Answer 4

In the figure attached A,B,F1 and F2 are packages. On s = On Success and On f = On Failure.

If you build all the packages as shown in the figure below, and Execute them all together, everything works fine. However, if you first build A and B and later on add F1 and F2 (to execute on Failure of A and B respectively), F1 and F2 fails to execute when there is failure in A or B. On checking the sequence of Execution, F1 and F2 are placed after B.

Is there a way I can incorporate F1 and F2 in the packages without having to redo the everything from fresh? Thanks.

Nicholas Cain SSC-Dedicated Points: 33009 More actions · Answer 5

I can't see the figure.

Let's just say though that you have step A and B and you want to add failures...

A --success--> B

| |

failure failure

| |

C Copy of C

Don't have

A --success--> B

| |

failure failure

| |

----->C<-------

Shamless self promotion - read my blog http://sirsql.net

jo Mong Say Hey Kid Points: 698 More actions · Answer 6

Correct, I have

A --success--> B

| |

failure failure

| |

C Copy of C

but if I previously compiled/executed A --Success-->B before adding C and Copy of c,

on adding C and copy of C, C fails to execute when A fails. Is this a mistake on my side?

Workflow Properties Precedence of C shows:

Source step = A, Precedence = failure and Destination step = C

imhappy SSC Enthusiast Points: 105 More actions · Answer 7

I think that you have set FailOnError or FailPackageOnError of any step to be True. If FailOnError or FailPackageOnError to be True, the package will stop its execution wherever the error occurs!