SSIS Package Configurations

Working with SSIS packages can cause problems when you have to develop across different environments. Dougbert.com links to some SQL MVPs in a short blog post. They describe how you can tackle these problems with SSIS Package Configurations.

First, it helps to know what SSIS Package Configurations are exactly. Rafael Salas has written a nice entry on the Microsoft MSDN site in which he explains in fine detail what configurations are and which options you have in SSIS to use them. In a nutshell: you use Package Configurations to make static values in your SSIS package configurable, so you can change them from outside. Think, for example, of database names in your connection managers.

For the exact uses of Package Configurations and ideas on how best to set up an approach for configurations, this MSDN post is very useful. John Welch has written a good article about it, in which he explains which different approaches are possible to make your SSIS packages configurable.

Finally, there is our SSIS Junkie, who of course also has an opinion about Package Configurations. Jamie Thomson has written a piece on MSDN about best practices with Package Configurations.

These articles give a clear picture of what Package Configurations do exactly and how to apply them. When you develop SSIS packages in a team with a complete DTAP setup (Development, Test, Acceptance, Production), for example, it is certainly a good idea to look at how Package Configurations can make your development easier.