![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I have following workflow to be implemented in my dts package. s s s s s step1 ---> step2--->step3--->step4--->step5--->step6 Now If step1 OR step2 OR step3 OR step4 OR step5 OR step 6 fails i want to execute step7. As OR is not available, in order to implement this i will need to have six different step icons, one for failure of each step from step1 to step6. I read following Darren's article for OR processing. http://www.sqldts.com/default.aspx?218 But if i implement this idea, i will have to write very long code. Please help me on this. Thanks, Pradeep |
#3
| |||
| |||
|
|
In message <2fe85a61.0402141732.5fa128 (AT) posting (DOT) google.com>, pradeep pradeep.mittal (AT) citigroup (DOT) com> writes Hi, I have following workflow to be implemented in my dts package. s s s s s step1 ---> step2--->step3--->step4--->step5--->step6 Now If step1 OR step2 OR step3 OR step4 OR step5 OR step 6 fails i want to execute step7. As OR is not available, in order to implement this i will need to have six different step icons, one for failure of each step from step1 to step6. I read following Darren's article for OR processing. http://www.sqldts.com/default.aspx?218 But if i implement this idea, i will have to write very long code. Please help me on this. Thanks, Pradeep Pradeep, There is no reasonable way of doing this. The article you mention demonstrates the only way it can be done, but as you say it involves a lot of code and is not easy to maintain, and I would not recommend using it for something like this, it is just too much work. Having individual error tasks does have some advantages, in that you can code information about the failed step and also any potential clean-up logic specific to that task. The only other alternative is to try and make better use of the logging options in DTS and use that to do what you need to achieve. |
![]() |
| Thread Tools | |
| Display Modes | |
| |