JustMarie (9/28/2016)
Using the SSISDB catalog requires project level deployment. That's something to consider when researching this. For companies that have been doing package level deployment for years this is going to be a major change and may not be a welcome change.My company uses Control M to batch jobs. That requires config files. Moving to the catalog isn't an option. So config files are created and put into source control.
There are two type of configuration used by SSIS
1. Direct (hard-coded) XML file path configuration.
2. Indirect Configuration (Environmental Variable).
Both have pros and cons and have deployment related issues. Its better to understand them before proceeding further.
Following link contain details understanding for both:
Deploying SSIS Packages with XML Configurations[/url]
Indirect VS Direct configuration
Is it possible to avoid XML config files and still use package configuration in SSIS?