Saturday, February 22, 2014

Execute Package Task


The Execute Package Task enables you to build SSIS solutions called parent packages that
execute other packages called child packages. You’ll find this capability an indispensable part of
your SSIS development as your packages begin to grow.
 
Separating packages into discrete functional workflows makes for shorter development and testing cycles and facilitates best development practices. Though the Execute Package Task has been around since the legacy DTS, several improvements have simplified the task. First, the child packages can be run as either in - or out - of - process executables.

In the Package tab of the Task Editor, you can see the new ExecuteOutOfProcess property, which if set to the default value of false, will execute the package in its own process and memory space. Another key difference is that the parent package no longer pushes parameters to the child package. Instead, the child package is aware of and can reach into the parent package to access parent - package - level configuration values. The majority of the configurable properties are in the Package tab of the Execute Package Task Editor.
The first option is to provide the location of the child package. The options here are File System and SQL Server. You can deploy an SSIS package in the File System Task as a .dtsx file, or within the msdb database of a SQL Server instance. If you select File System, you must first create a new Connection Manager connection to the package by selecting <New Connection . . . > from the Connection drop - downbox. If the child package is located in a SQL Server, you ’ ll need to provide the OLE DB Connection Manager for the SQL Server that holds your package. In either case, browse to and then select the child package within the connection to set the package to execute in the task.

SSIS Interview Question , SSIS Interview questions and anwers

No comments:

Post a Comment