Export (0) Print
Expand All

Creating a Deployment Utility

Updated: 5 December 2005

The first step in deploying packages is to create a deployment utility for an Integration Services project. The deployment utility is a folder that contains the files you need to deploy the packages in an Integration Services project on a different server. The deployment utility is created on the computer on which the Integration Services project is stored.

You create a package deployment utility for an Integration Services project by first configuring the build process to create a deployment utility, and then building the project. When you build the project, all packages and package configurations in the project are automatically included. To deploy additional files such as a Readme file with the project, place the files in the Miscellaneous folder of the Integration Services project. When the project is built, these files are also automatically included.

You can configure each project deployment differently. Before you build the project and create the package deployment utility, you can set the properties on the deployment utility to customize the way the packages in the project will be deployed. For example, you can specify whether package configurations can be updated when the project is deployed. To access the properties of an Integration Services project, right-click the project and click Properties.

The following table lists the deployment utility properties.

Property Description

AllowConfigurationChange

A value that specifies whether configurations can be updated during deployment.

CreateDeploymentUtility

A value that specifies whether a package deployment utility is created when the project is built. This property must be True to create a deployment utility.

DeploymentOutputPath

The location, relative to the Integration Services project, of the deployment utility.

When you build an Integration Services project, a manifest file, <project name>.SSISDeploymentManifest.xml, is created and added, together with copies of the project packages and package dependencies, to the bin\Deployment folder in the project, or to the location specified in the DeploymentOutputPath property. The manifest file lists the packages, the package configurations, and any miscellaneous files in the project.

The content of the deployment folder is refreshed every time that you build the project. This means that any file saved to this folder that is not copied to the folder again by the build process will be deleted. For example, package configuration files saved to the deployment folders will be deleted.

ms137952.note(en-US,SQL.90).gifNote:
To become better acquainted with the concepts explained in this section, see Deploying Packages Tutorial.

Release History

5 December 2005

Changed content:
  • Described how rebuilding a project refreshes the deployment folder.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft