Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Execute data flow task Expand / Collapse
Author
Message
Posted Wednesday, April 17, 2013 11:55 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 7:02 AM
Points: 63, Visits: 562
Hi All,

I have an existing complex package with lots of data flow tasks grouped in different sequence container. Previously it was running as a whole single unit. Now the requirement has changed i need to execute few selected dataflow task in a different schedule.
For e.g.

In sequence container 1--> Dataflow task1 needs to run monthly on 11th.
In sequence container 2 --> Dataflow task3 needs to run daily
In sequence container 3 --> Dataflow task4 needs to run monthly on 5th.
And on 20th the whole package except the above dataflow tasks.

I know if i can create separate packages based on the above schedule requirement then it will work, but is it possible to handle that programmatically through some script task where i will load the above package run time, then based on parameter i can execute the required dataflow task of the selected sequence container, or is there any other option without making any changes to main package it self.

Please suggest how to handle the above requirement without making any change to the existing package .



Thanks in advance
Sam
Post #1443409
Posted Wednesday, April 17, 2013 2:21 PM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Friday, September 19, 2014 2:29 PM
Points: 1,480, Visits: 1,031
You could do this using workflow and Expressions.
But I wouldn't. I try to make all packages do a simple job or task, then chain packages together. Helps testing, isolation of bugs etc. If you do, I would use variables that are populated at runtime of the schedule these separate tasks should run. that way when they change their mind again you just change the schedules. Not modify the package each time.

Create a Script Task before the sequence container, or as the first step within the sequence container.
In the script task figure out if it should run or not, if yes set a variable. Then evaluate that variable in the Precedence Constraint.

Quick Tutorial here
http://www.sqlis.com/sqlis/post/Introduction-to-Expressions-on-Workflow.aspx
Post #1443487
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse