I doubt this is feasible. Rather I would simply run some kind of a job just before the parent package starts in which I would detect if the [Dev] server is online and if not modify/change or point the Environment variable to whatever else is applicable.Arthur My Blog

I'm not sure if this is possible, but I'll try to best explain what I would like to do. The server setup we have is out of my control, but we have one SSIS server which is used for multiple database environments (dev, test, prod). We also have 1 version of each package that we dynamically configure at run time to point to the correct "config" database for the environment it is running for, using an environment variable configuration. I have a standard master/child package setup and each connection manager in the child packages have their connection strings configured by a parent package variable configuration. I have run into some problems with this, because SSIS will validate the run time connection strings (usually our development servers) before applying the parent package configurations. If our dev server is down for maintenance, this causes issues in production. I could set DelayValidation = TRUE on everything, but that is a last resort at this point. What I would like to do is be able to have the master package run a script task (or something that will do the same thing) which will go into to each child package and update the environment variable configuration that is used to point to the "config" database. This will get me around having to use parent package variable configurations and every configuration can be SQL Server based after I get the "config" connection string set correctly. Any help is appreciated. Thanks

I doubt this is feasible. Rather I would simply run some kind of a job just before the parent package starts in which I would detect if the [Dev] server is online and if not modify/change or point the Environment variable to whatever else is applicable.Arthur My Blog