Package Configurations not so portable? - MSDN Forums

 

The best way we've found is to:

1. Edit the package and create an XML configuration file with the properties you need.
2. Save the file to a known location
3. Create a system variable
4. Populate the variable with the full path and file name of the above XML file
5. Edit the package and remove the package configuration for the XML file.
6. Create a new configuration of type Environment variable and type in the name of the system variable
7. The new package configuration should show with "Indirect XML configuration file" once the above has been done.

This can obviously be tuned to take keeping packages in the dark into account etc. etc.

Source: Package Configurations not so portable? - MSDN Forums

 

 

Everyone seems to be trying to solve the issue of the XML file path being stored in the configuration organizer and that in turn requiring all file system environments having the same structure.  If you are storing the package in a file system as opposed to MSDB, there is a very easy solution  .... remove the path and leave just the XML file name.  The XML config file will then need to be in the same folder as the package, but it then becomes file structure independent.

Further, the tool (SSIS) should not dictate whether it is a good idea or not to maintain similar file structures across environments.  Whether it is a good idea (personally I believe it is) the tool should support a reasonable solution.