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.
Select Project Reference for child packages that are in the project. Select External Reference for child packages that are located outside the package
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.
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.
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
Select the location of the child package. This property has the options listed in the following table.
Set the location to an instance of SQL Server.
Set the location to the file system.
Select the type of storage location for the child package.
Displays the package name.
ReferenceType = Project Reference
Select a package contained in the project, to be the child package.
Location Dynamic Options
Location = SQL Server
Select an OLE DB connection manager in the list, or click <New connection...> to create a new connection manager.
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.