Hi,At design time I use a local Config (XML) for SSIS packages. When the package is put in production SQL Server is used to assoiate a different server based (xml) config file. The package(s) run fine butI just noticed that they are attempting to load the design time config file (Event log).Other than demoving/deleting the design time reference (which would then need to be added each time a change is required) is there a way to "publish" the package without the reference to the design time config?Thanks in advance,O

The best way to do this is with "Indirect Configurations" where you setup an environment variable on all machines where the packages will be built - your desktop, dev server, test server, prod server, etc...This environment variable points to a specific configuration file. It is fully qualified like so: c:\ssis configs\dev_config.dtsConfig. In prod you might have: c:\ssis configs\prod_config.dtsConfig, or you might simply have the same named file in each environment.This path would go in the environment variable you setup. Then in the SSIS package, change the XML Configuration binding to use an environment variable as the source. Now wherever you deploy the package, it will use whatever config file is specified in the environment variable.Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer

Is there a way to programmatically update the environment variable before running the package then? I have a package that gets run on the same machine but with different config files for different data load source files. So I need to change the config value on each run. But I'm having the same pain as OBM - it means I have to delete the config before deploying and add back when modifying.