Microsoft SQL Server 2012 Bible

Deploying and Executing Projects and Packages

Once a package is developed and working properly, it must be deployed to a server where it can be executed to perform its designated tasks. In this section the new Project Deployment Model is explained, as well as the Package Deployment Model (sometimes referred to as Legacy or File deployment).

Using the Package Deployment Model

Package Configurations used to be the only way to enable developers to quickly deploy packages between servers and environments, providing a way to set properties within the package based on environment-specific configurations. Although effective, the learning curve for this method of configuring packages proved to be one of the most challenging features to learn. There are, however, countless multipackage solutions deployed to production systems at this moment that utilize this deployment model, and therefore this method deserves careful consideration.

To access Package configurations, first make sure that your project is in Package Deployment Mode. The words (package deployment model) will be beside the project name in Solution Explorer. If it is not in package deployment mode, change it by right clicking on the project and selecting Convert to Package Deployment Model from the menu. Open the Configurations dialog box by going to the SSIS menu. Select SSIS → Package Configurations. Configurations are applied to the package in the order they are listed here. To add a new configuration, ensure that configurations ...