Package Configuration in SSIS

As we develop, test and deploy SSIS packages, we need to specify different parameter values for things like database connection strings, file and folder paths, etc. without having to edit the individual SSIS packages to make these changes.

SSIS provides several options for handling package configuration values such as environment variables, XML files, registry settings, and a table in a SQL Server database.  In each case you are storing and maintaining configuration parameter values outside of the SSIS package then using those stored values when executing the package.  There are several advantages to using SQL Server package configuration over the other options such as:

    Storing package configuration values in a SQL Server database rather than on the file system or in the registry allows us to include this data in our standard SQL Server backup and restore plans.
    Changing the configuration data can be done with simple T-SQL commands such as INSERT, UPDATE and DELETE.
     DBAs are usually more comfortable working with SQL Server tables than XML files or registry settings.