Section 7

Configuring Packages

  • Lesson 44: Easing Deployment with Configuration Tables
  • Lesson 45: Easing Deployment with Configuration Files
  • Lesson 46: Configuring Child Packages

Chapter 44

Easing Deployment with Configuration Tables

Once you have completed a set of packages, the challenge is to deploy those packages to a production environment without having to manually reconfigure them for that environment. For example, you may have to get source files from a different directory or the source databases may be on a different server than your production environment.

NOTE New project deployment options in SSIS 2012 use parameters and environments. These are covered in Lessons 33, 53, 54, and 57. This chapter and the next cover configuration tables and configuration files, which are still supported in the current release. You must decide if the packages in your project will use the new project deployment model or the package deployment model.

Configuration tables help automate migration and reduce the risk of deployment-related errors. You can use a configuration table that contains the ConnectionString property value for each connection. Each package that uses the connection can obtain the ConnectionString from the configuration table. As part of the initial deployment to production, you create another configuration table, like the one used in development. You then copy the rows from the development configuration table to the production configuration table, changing the ...

Get Knight's Microsoft SQL Server 2012 Integration Services 24-Hour Trainer now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.