Connection Manager Deployment with master/detail package

Hallo,

I'm currently strugling with the setup of our packages for deployment to a new environment.

We are working with a master/detail package setup. One master package is created that will call all child packages. In the master package we don't have any connection towards our source and/or target databases/sourcesystems.

Everything works fine, however, starting to deploy the whole set of packages, it seems that we don't have the option to set specific properties of our detailed packages, e.g. connection properties. But this is just what we need.

When we are adding a job in the Job Agent for our master package to be scheduled, we want to be able to set all different connection manager properties, not only the one from the master package and definitely the ones from the detailed packages as there we switch the connections from the development environment towards the acceptance environment.

I tried to fix this with parent package variables, but I can't set the password property, only the ServerName and UserName can be set, not the Password.

Anyone an idea what the easiest and best approach is to solve this burden?

Thx

Children packages should use package configuration on their connection strings as well; then when deploying the packages to a different enviroment all you have to do is to change the configuration values.

Be warned that there is a known bug when using package configuration with 'parent variables' that, under certain circustances may prevent you to set connection in children packages properly. See details here: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126146

Because of that, my recommendation is to define package configurations to set connection strings on every child package(via XML file, SQL server table, env. variable, etc).

"When we are adding a job in the Job Agent for our master package to be scheduled, we want to be able to set all different connection manager properties, not only the one from the master package and definitely the ones from the detailed packages as there we switch the connections from the development environment towards the acceptance environment. "

I think you can only set properties of the invoked package from the command line...as I said before; use configuration packages for that.