We are trying to deploy our first SSIS packages to our production environment (SQL Server 2008 R2). We are using an environment variable, SSIS_CONFIG, to contain the connection string of the database that contains our SQL Server configuration table dbo.SSIS Configurations where the remainder of our connection strings are located. Everything is working fine in our development environments but when we are moving to production we are having some issues. Our project contains a Master package that calls 6 child packages to replicate some data from our DB2 mainframe environment down to our SQL Server environment. We have verified that the SSIS_CONFIG variable on production is pointing to our production server and we have loaded the rows in our production dbo.SSIS Configurations table to point to the correct production connection strings. When we deploy the project to the MSDB in Integration Services on the production server and execute the Master package it shows in the connection manager that it is using the production connection string for our production dbo.SSIS Configurations table. However when we run the Master package the child tables still contain the development connections strings and appear to ignore the values in the production Configurations table. At that point I thought I might need to add the SSIS_CONFIG variable to each of the child packages' configurations although I never read any documentation that made me believe this would be required. When I made that change and deployed the project to production it appeared that the production connection strings were being picked up. If I run the master package the configuration manager shows the updated production connection string but when the package runs the Master package uses the production connection string but the child packages continue to use the development connection strings. I then tried to run one of the child packages independently and it too shows the production connection string and when run independent of the master package it does use and update the production tables. It only uses development connection strings when it is called from a master package. To make things more confusing I have deployed a small test package to our production environment that contains one master package and two child packages using this same environment variable, same SQL Server configuation table and same connection strings and it is working. I also only have the SSIS_CONFIG, environment variable listed in the Master package for that project - not in the child packages. Why would the configurations, connection strings and environment variables work for one package but not for others? What could be the difference?

Please read this article on how the config values are being applied: http://dougbert.com/blogs/dougbert/archive/2009/04/07/understand-how-ssis-package-configurations-are-applied.aspxArthur My Blog