I have an SSIS 2008 package with a single configuration named Config. I would like to use the
dtexec /SET switch to change the path of the config file that it uses so our developers that build the package can have it point to their local path, but when we deploy it to our production servers we can specify a new path for dtexec to load the config from so it can contain prod settings.
According to MSDN we should be able to do this using the /SET command as it mentions here:
Using the /Set option to change the location from which the utility loads design-time configurations Behavior in SQL Server Integration Services 2008
After the utility applies the run-time options, the utility reloads the design-time configurations from the new location.
dtexec /FILE "PackagePath" /SET "\Package.Configurations[Config].Properties[ConfigurationString]";"ConfigFilePath"
and it fails with:
The package path referenced an object that cannot be found: "\Package.Configurations[Config].Properties[ConfigurationString]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
I realize there are other ways of doing indirect configs using environment variables, etc... but that is not what I'm interested in so please do not offer up those suggestions. I'm specifically trying to use the /SET command since Microsoft has explicitly stated that we should be able to. Due to the way our environment is setup this method would be the best for us.