Execute Package Task

Additional information

License

SQL Server Version

, , , , ,

Vendor

Description

The Execute Package task in SSIS allows users to call packages that are part of the Same Project, File system, and SQL Server. It extends the enterprise capabilities of Integration Services by allowing packages to execute other packages.

The Execute Package Task is used with a number of purposes:

  1. Running packages;
  2. Breaking down a complex package workflow, Which makes them easier to read, test, and maintain;
  3. Reusing parts of packages. Other packages can reuse parts of a package workflow;
  4. Grouping work units;
  5. Controlling package security. By separating a package into multiple packages, you can provide a greater level of security, because you can grant an author access to only the relevant packages;
  6. Extending transactions;
  7. Propagating Logging Details.

Let’s see what’s in the package.

 –  Find the Execute Package Task in the SSIS Toolbox and drop it on top of the Control Flow area;
 –  Double click on the task;

General Tab

Change the name of the Task and add/change the description.

Package Tab

  1. Reference Type – this tells the task where the package that we want to run, exists;
    1. Project Reference is for packages that exist within the project;
    2. External Reference is for packages that have already been deployed to a server that you would want to reuse;
  2. PackagesNameFromProjectReference – will allow us to select a package that exists within the project, when the Project Reference type is selected. This will be a child project;
  3. If the user selects External Reference, the Editor will ask the user to enter a Location, a Connection, and a Package Name for the package the user is trying to access;
    1. Selecting the SQL Server location, will ask for a Connection and the PackageName, which can be written or selected by clicking on the ellipsis (…).
    2. Selecting the File System location, will ask for a Connection and will display the name of the package below.
  4. Password – will let you enter a password for the package you’re trying to execute, in case it is password protected;
  5. ExecuteOutOfProcess – switching this to true will spawn a separate process to run this package outside of the process that is being used to run the Parent.dtsx package.

Parameter Bindings Tab

Child package parameter – this sets the name of the parameter that we will be receiving the passed value. Change NewParameterName to Process_MemberFileName.

Binding parameter or Variable: This drop down contains any package parameters or variables accessible to our current package that we will be passing values from.