0 out of 1 rated this helpful - Rate this topic

Execute Package Task Editor

SQL Server 2012

Use the Execute Package Task Editor to configure the Execute Package Task. The Execute Package task extends the enterprise capabilities of Integration Services by letting packages run other packages as part of a workflow.

What do you want to do?

Open the Execute Package Task Editor
Set the Options on the General Page
Set the Options on the Package Page
Set the Options on the Parameter Bindings Page

Open the Execute Package Task Editor

Open an Integration Services project in Visual Studio that contains an Execute Package task.
Right-click the task in the SSIS Designer, and then click Edit.

Set the Options on the General Page

Name

Provide a unique name for the Execute Package task. This name is used as the label in the task icon.

Note
Task names must be unique within a package.

Description

Type a description of the Execute Package task.

Set the Options on the Package Page

ReferenceType

Select Project Reference for child packages that are in the project. Select External Reference for child packages that are located outside the package

Note
The ReferenceType option is ready-only and set to External Reference if the project that contains the package has not been converted to the project deployment model. For more information about conversion, see Deploy Projects to Integration Services Server.

Password

If the child package is password protected, provide the password for the child package, or click the ellipsis button (…) and create a new password for the child package.

ExecuteOutOfProcess

Specify whether the child package runs in the process of the parent package or in a separate process. By default, the ExecuteOutOfProcess property of the Execute Package task is set to False, and the child package runs in the same process as the parent package. If you set this property to true, the child package runs in a separate process. This may slow down the launching of the child package. In addition, if set the property to true, you cannot debug the package in a tools-only install; you must install the Integration Services product. For more information, see Install Integration Services.

ReferenceType Dynamic Options

ReferenceType = External Reference

Location

Select the location of the child package. This property has the options listed in the following table.

Value	Description
SQL Server	Set the location to an instance of SQL Server.
File system	Set the location to the file system.

Connection

Select the type of storage location for the child package.

PackageNameReadOnly

Displays the package name.

ReferenceType = Project Reference

PackageNameFromProjectReference: Select a package contained in the project, to be the child package.

Location Dynamic Options

Location = SQL Server

Connection

Select an OLE DB connection manager in the list, or click <New connection...> to create a new connection manager.

PackageName

Type the name of the child package, or click the ellipsis (…) and then locate the package.

Location = File system

Connection

Select a File connection manager in the list, or click <New connection...> to create a new connection manager.

PackageNameReadOnly

Displays the package name.

Set the Options on the Parameter Bindings Page

You can pass values from the parent package or the project, to the child package. The project must use the project deployment model and the child package must be contained in the same project that contains the parent package.

For information about converting projects to the project deployment model, see Deploy Projects to Integration Services Server.

Child package parameter: Enter or select a name for the child package parameter.
Binding parameter or variable: Select the parameter or variable that contains the value that you want to pass to the child package.
Add: Click to map a parameter or variable to a child package parameter.
Remove: Click to remove a mapping between a parameter or variable and a child package parameter.

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Additions

ADD