Re: How to force a SSIS package step to fail?
- From: "Steen Schlüter Persson (DK)" <steen@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Mar 2008 13:05:06 +0100
Hi J,
I've also looked into this solution and it might also be what I'm going to do. I just thought that there was another way where I could force the step to fail and then use the "original" Success/Failure/Completion constrain.
Regards
Steen
jhofmeyr@xxxxxxxxxxxxxx wrote:
Hi Steen,.
Why would you want the package to fail? In DTS (SQL Server 2000) you
could "fail" steps in order to control package flow, but his is not
necessary in SSIS. If you want the package to follow a different
control flow depending on the outcome of the stored procedures, you
can use conditional expressions based on the return values.
To do this, double-click on the connector line joining 2 of your
ExecuteSQL tasks and change the "Evaluation operation:" to any of the
options that include "Expression". This enables you to enter a
boolean expression that must evaluate to true for the path to be
followed. Assuming you've got an int parameter called "sp1rtnvalue"
which must evaluate to 1 for the flow to continue; your expression
would be:
@sp1rtnvalue == 1
Good luck!
J
- Follow-Ups:
- Re: How to force a SSIS package step to fail?
- From: "Steen Schlüter Persson (DK)"
- Re: How to force a SSIS package step to fail?
- References:
- How to force a SSIS package step to fail?
- From: "Steen Schlüter Persson (DK)"
- Re: How to force a SSIS package step to fail?
- From: jhofmeyr
- How to force a SSIS package step to fail?
- Prev by Date: Re: SSIS & Script Transformation (debug vs normal)
- Next by Date: RE: SSIS Expression Builder Replace function
- Previous by thread: Re: How to force a SSIS package step to fail?
- Next by thread: Re: How to force a SSIS package step to fail?
- Index(es):
Relevant Pages
|