Control Flow setup

Hot Topic

Report builder & designer end-user's functionality
Requirements for Sql Server Mobile and Sql Server 2003 interaction
Update Statement not working
Data driven Subscription
Datafields in report header
File System Task Error
SetDefaultInitFields "TextBody" for Stored Procedure
How to flag a row and allow max one row flagged in the table.
Trigger question
Evaluating String Content

SQL Server

Is there such a thing as Data-Driven Snapshots?
Passing parameter to a dts
Multiple details sections, possible?
Nulls when summing a group in an expression
SP with SSIS and 2005 database
SQL 2005 woes
Replicate data only from SQL Express to SQLserver2005
RDA Pull Error table
Problem updating SQL2005 From MSAccess Form
ReportServer giving me a 404????

Control Flow setup

Is it possible to setup a Control Flow at the solution level rather than at the package level I'd like to setup a Control Flow that truncates multiple tables in a staging database then runs multiple packages that reloads those tables. Each package has a Control Flow tab that seems to be specific to the package. Is it possible to set something up that governs the execution of multiple packages

Thanks.

Answer this question

Control Flow setup

  • Newsco

    SSIS contains a task called the "Execute package Task" which does it exactly what it says on the tin. It is ideally suited to the scenario you mentioned.

    -Jamie



  • SHANOND

    lwrich wrote:
    Since the control flows are all at the package level, if you have a solution with multiple packages, you probably need to just pick a control flow from one of the packages and use that control flow to run all the packages at once using the 'execute package task' you mentioned.

    I'm not understanding why that is a problem. Can you elaborate

    lwrich wrote:

    There should be control flow objects at the solution level that control the running of all packages. Most etl tools have this.

    This isn't meant to be as rude as it sounds but I couldn't disagree more. SSIS has this i.e. control-flow objects to control the running of packages as well - packages themselves. It seems you are suggesting that we use SSIS packages for "work" and a completely different tool for workflow.

    SSIS packages have a a workflow engine built into them so why would you use something else

    That's not rhetoric. I'm interested to hear your views here.

    -Jamie



  • Reiguz

    Since the control flows are all at the package level, if you have a solution with multiple packages, you probably need to just pick a control flow from one of the packages and use that control flow to run all the packages at once using the 'execute package task' you mentioned. There should be control flow objects at the solution level that control the running of all packages. Most etl tools have this.
  • Control Flow setup
Answer this question