Ideally, you could have a single Master package calling each of your 100 packages which I assume are performing specific tasks. In this Master package, you can pass the Connection Manager
details to each 'Child' package during run time itself. The way this is done is by creating variables in each package to hold the server name and database name, and then to update the ConnectionString
property in each child package at the start of execution. That way, you only need to generate 1 configuration file for the Master package, and you can configure the database connection parameters as you want. However, this will entail extra development effort as follows:
- A new SSIS package to act at Framework level and co-ordinate running the 100 packages
- Variables in the new and existing packages to hold server name and database name
- A new configuration file in the Master package
The alternative is to just generate configuration files for each of the 100 packages. Then, you will have a separate file for each package, but you will need to make your replacements in each of the configuration files.
You can check out the below links for resources on this:
Connection Manager
server and database names? Do you have configuration files to allow you to change this data depending on environment? - shree.pat18