July 24, 2014 at 9:18 am
Hello,
I have about 120 SSIS packages and one single CONFIG file. I also have a master package that runs each child package in a specific folder (all 120 of them). When I open the individual packages the connection managers all point to our production server, so I altered the config file to point to our development box. I assume that the config file will override any connection managers in the child packages? I am concerned about populating our production tables instead of development. Is this correct or do I have to open each package and change the connection managers. :ermm:
Thanks in advance!
SQL-TG
The are no problems, only solutions. --John Lennon
July 24, 2014 at 9:59 am
It can work either way. Usually, the child packages would be set to either inherit a variable from the parent, or they'd all be set to pick up the value from the same config file, but it's equally possible to have them inherit nothing at all.
So, I'd tread cautiously and check what the design pattern is first. Look at a few child packages and check their package configuration settings. I might even hack the host file for the test environment where you're running the packages from to make sure it can't even get to the prod environment in case you miss something!
July 24, 2014 at 12:07 pm
Thanks Howard. Much appreciated.
The are no problems, only solutions. --John Lennon
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply