May 13, 2005 at 7:09 am
hiya- i have a package and ie set the flow up so that certain tasks will only run when others have completed using the 'on completion' workflows. however, some appear to run from the start which is not what i want.
Am i missing something?
A.lex
May 13, 2005 at 11:09 am
I am just now looking at a similar issue, and I was wondering:
Is the first task an ExecuteSQL task, and, if so, does the task contain GO statements separating things into batches?
My current speculation is that the GO (signalling an end of batch) is triggering the ON SUCCESS condition, even though there are multiple other batches in the ExecuteSQL task. I am speculating that removing the GOs (or splitting the tasks into multiple chained ExecuteSQL tasks) will correct the error, but, since you are having this same issue right now, I was wondering if the problem is the same.
If my speculation is correct, I would call this a DTS Bug (or an 'undocumented feature', if you prefer).
May 13, 2005 at 12:27 pm
Not sure if this will help either one of you but...
This site has some execellent examples of controlling workflow through ActiveX Scripts.
May 16, 2005 at 6:58 pm
Well, the changes I made (splitting the separate SQL Statements into multiple different Execute SQL tasks) fixed the problem entirely. So, this is a new warning:
In DTS Packages, do not use GO in Execute SQL Tasks that have an On Completion / On Success exit point.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply