![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all I am generating an error in one step so the dts execution will flow to a different direction than the one it would normaly choose (on that step's success). The thing is that when I schedule it in to a job the step's failure fails the job.. although the package continues successfuly to the rest of the following steps. How should i prevent the job from failing in this case?? Thank you very much Rea |
#3
| |||
| |||
|
|
The only thing to do is to prevent any steps from failing during execution. Some strategies that may help- How can I check if a file exists? (http://www.sqldts.com/default.aspx?211) Skip the execution of an individual Task (http://www.sqldts.com/default.aspx?214) -- Darren Green http://www.sqldts.com "Rea Peleg" <rea_p (AT) afek (DOT) co.il> wrote in message news:e%23GqL6K$EHA.3236 (AT) TK2MSFTNGP15 (DOT) phx.gbl... Hi all I am generating an error in one step so the dts execution will flow to a different direction than the one it would normaly choose (on that step's success). The thing is that when I schedule it in to a job the step's failure fails the job.. although the package continues successfuly to the rest of the following steps. How should i prevent the job from failing in this case?? Thank you very much Rea |
#4
| |||
| |||
|
|
Thanks alot Darren! Then the only time you would use the 'on failure' workflow option in dts will be to perform cleaning actions before the package and its job end.. Rea |
![]() |
| Thread Tools | |
| Display Modes | |
| |