I have an SSIS package that is using a SQL Server configuration to store connection strings for the other connection managers used by the package. The connection string for the connection manager used to get the SQL Server configuration data is passed
to DTExec when the package is executed. The SQL configuration sets the values of variables that hold the connection strings and the connection managers use the variables in an expression to set the connection string. I'm doing this so that I can
move the packages from dev to qa then to production.
I also need to have the child packages use the same connection strings as the parent package so each child package has a parent package variable configuration containing the connection strings. It uses these to set the values of child package variables
which are then used to set the connection string property of the connection managers using an expression.
I tested my packages by connecting to the development SSIS server, clicking on the package and selecting run package. I select the connection managers tab so that I can change the connection string of the connection manager that points to the SSIS
Configurations table which contains the development connection strings. This works great.
I deployed my packages to the production server and again tested the packages by running them from the pr
View Complete Post