Greetings- We are seeing strange behaviors in SSIS when converting our packages from 2005 to 2008. In 2005 when we move our dtsx files to our test and integrated environments all we did was change the path to the config file in the SQL Job Screen or using the execute utility and the package has no problem pulling in these config settings from this config file. In 2008 we are seeing something different. When we move the dtsx to the new environment and then set the path to the new config file in the SQL Job Step screen under the Configurations tab it cant read the config file. For some reason in 2008 the path given in SQL Job Step OR using SSIS Package Execution Utility wont override the path inside of the dtsx? This is a departure from 2005 where this wasnt the case and forces us to have to open and update every package when we migrate from one environment/location to the next. Anyone know how to get around this in 2008 ? Is this a bug in the converter? Thanks

This is related to the order in which the configurations (design-time and runtime) are loaded.Check out http://msdn.microsoft.com/en-us/library/bb500430.aspxfor a discussion behavior differences between 2005 and 2008.There is also a goodarticle written by jwelch on this.Hope that helps.

There is now an open source utility available in CodePlex which can be used to batch update SSIS Package Configuration File paths without using BIDS or manually editing the package XML: http://ssisconfigeditor.codeplex.com/