I have a SSIS parent package and multiple child packages in a project for a
DW load, and looking to deploy the project across multiple environments
(dev/test/prod). In the past, *.udl files were used in DTS to manage the
connections when moving across environments. In SSIS, I want to use a
single master configuration file to be able to reference the connection
information for source and destination for the proper environment. In
BIDS, I can reference a single XML configuration file to support the
different environments, but when the deployment utility is specified, it
causes and error when each package tries to write to the same *.config file.
I want to be able to eventually deploy the project to the SSIS service in the
proper environment. Is there best practices in deploying a parent (load
group package) and its child packages across environments?