I have been reading a few other threads on this topic but so far nothing is helping. My ETL package runs perfectly in my development environment but my attempts to create package configurations so that things like connection strings can be changed
for the production environment without modifying the package are not working... To be clear I can get things like the connection string to my "target" ETL database to work just fine using an XML config file. However I seem to be running
into a problem where even though at run-time my package may pay attention to certain config settings, it first validates the development settings (which are not right in the production environment hence it fails).
On this microsoft page ->http://msdn.microsoft.com/en-us/library/ms141682.aspx under the section entitled "Understanding How Package Configurations are Applied at RunTime" it says...
"When you use the dtexec command prompt utility (dtexec.exe) to run a deployed package, the utility applies package configurations twice. The utility applies configurations both before and after it applies the options that you specified
on command line"
I think this may be the root of my problem... why in the world would it first apply the "before"configuration?!?!?! (ie
"the configuration before it applies the options" ) Afterall, the conf
View Complete Post