October 13, 2005 at 10:10 am
Is there a way to bypass certain SQL tasks in a package if certain criteria are not met? Basically pass the tasls a value that says they have been executed even though they have not.
Does anyone have an example?
October 13, 2005 at 4:44 pm
one way to get around...
Eg. say you 3 sql tasks as shown below and Task2 is the one to bypass
Task1-----------> Task2------------->Task3
From task1 - output a value to a global variable
from task2 - input the value from global variable then do a validation check. If condition not match do nothing (task will run but nothing happened).
Task3 will just pick up from task2 regardless.
October 13, 2005 at 10:29 pm
There are some good examples of this on SQLDTS.com
See http://www.sqldts.com/default.aspx?214 for some sample code.
October 14, 2005 at 6:10 am
Use a workflow Active-X script on your SQL Task (task 2). Check a global variable set in task 1. If the vaiable is set have you Main function execute the task. If not set Task 3 to a state of Waiting and set Task 2 to Do Not Execute Task.
-Mike Gercevich
October 14, 2005 at 6:10 am
Use a workflow Active-X script on your SQL Task (task 2). Check a global variable set in task 1. If the vaiable is set have you Main function execute the task. If not set Task 3 to a state of Waiting and set Task 2 to Do Not Execute Task.
-Mike Gercevich
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy