Re: How to force a SSIS package step to fail?
- From: jhofmeyr@xxxxxxxxxxxxxx
- Date: Thu, 13 Mar 2008 04:27:53 -0700 (PDT)
Hi Steen,
There is no concept of "Length" in a package string variable - it is
as long as you make it.
Try deleting and re-creating the ExecuteSQL task. Sometimes when you
change a stored proc the metadata in SSIS doesn't update correctly.
You might also consider changing your SP into a function if all it's
doing is returning a value...
I think using expressions is a better method of controling application
flow than Succ/Fail/Comp ... what happens if your task were to
actually fail?
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
- 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?
- From: "Steen Schlüter Persson (DK)"
- How to force a SSIS package step to fail?
- Prev by Date: RE: Membership download
- Next by Date: RE: How to handle DTS package when upgrade from sql server 2000 to
- 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):