![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
In page3 have more links... |

|
JFB "Jamie Thomson" <jamie.thomson (AT) int21 (DOT) com> wrote in message news:0f2601c37242$8a63cc30$a501280a (AT) phx (DOT) gbl... Hello, I have a multi-level package hierarchy and I'm worried about failures during scheduled dtsrun.exe executions. If a step in a package far into my hierarchy fails then what do I do? I don't want to have to run the whole thing again as normal as then all the steps that previously worked will get run again - and I don't want that. I see 2 options for getting around this. 1) Execute the whole package hierarchy under a single transaction. If a task fails, rollback the whole package hierarchy. This doesn't sound like a @good-practise@ method to me. 2) Have some way that a task checks to see if it should run, dependant on the progress of the whole package hierarchy (i.e. If I ran successfully last time but the whole thing didn't complete successfully, then don't run this time. How on earth do i do this though? Its something to do with workflow ActiveX scripts I guess but it seems like a huge task to try and accomplish. Is there a tried and tested method for doing what I want to do? I can't believe no-one has come across this problem before. Some code snippets would be fantastic. Thanks in advance. Regards Jamie |
#3
| |||
| |||
|
|
-----Original Message----- Hello, I have a multi-level package hierarchy and I'm worried about failures during scheduled dtsrun.exe executions. If a step in a package far into my hierarchy fails then what do I do? I don't want to have to run the whole thing again as normal as then all the steps that previously worked will get run again - and I don't want that. I see 2 options for getting around this. 1) Execute the whole package hierarchy under a single transaction. If a task fails, rollback the whole package hierarchy. This doesn't sound like a @good-practise@ method to me. 2) Have some way that a task checks to see if it should run, dependant on the progress of the whole package hierarchy (i.e. If I ran successfully last time but the whole thing didn't complete successfully, then don't run this time. How on earth do i do this though? Its something to do with workflow ActiveX scripts I guess but it seems like a huge task to try and accomplish. Is there a tried and tested method for doing what I want to do? I can't believe no-one has come across this problem before. Some code snippets would be fantastic. Thanks in advance. Regards Jamie . |
#4
| |||
| |||
|
|
How about my idea of putting the whole thing into a single transaction (Using "Join Transaction" in the workflow properties). Does anyone think this is a goer? The only problem I can see with it is that I don't think an Execute SQL Task (of which I have a few) can join a transaction. Thanks Jamie -----Original Message----- Hello, I have a multi-level package hierarchy and I'm worried about failures during scheduled dtsrun.exe executions. If a step in a package far into my hierarchy fails then what do I do? I don't want to have to run the whole thing again as normal as then all the steps that previously worked will get run again - and I don't want that. I see 2 options for getting around this. 1) Execute the whole package hierarchy under a single transaction. If a task fails, rollback the whole package hierarchy. This doesn't sound like a @good-practise@ method to me. 2) Have some way that a task checks to see if it should run, dependant on the progress of the whole package hierarchy (i.e. If I ran successfully last time but the whole thing didn't complete successfully, then don't run this time. How on earth do i do this though? Its something to do with workflow ActiveX scripts I guess but it seems like a huge task to try and accomplish. Is there a tried and tested method for doing what I want to do? I can't believe no-one has come across this problem before. Some code snippets would be fantastic. Thanks in advance. Regards Jamie . |
![]() |
| Thread Tools | |
| Display Modes | |
| |