January 11, 2012 at 12:59 pm
I have read the SSIS Package Configurations MSDN Article (http://msdn.microsoft.com/en-us/library/ms141682.aspx) and it states that:
You cannot use the /ConfigFile option to load configurations that replace the configurations that you specified at design time.
I need clarification on what this means exactly. Does it mean you can ONLY use the /CONFIGFILE parameter of DTEXEC if you did not specify any configuration files at development/deployment time?
January 11, 2012 at 2:30 pm
winston Smith (1/11/2012)
I have read the SSIS Package Configurations MSDN Article (http://msdn.microsoft.com/en-us/library/ms141682.aspx) and it states that:You cannot use the /ConfigFile option to load configurations that replace the configurations that you specified at design time.
I need clarification on what this means exactly. Does it mean you can ONLY use the /CONFIGFILE parameter of DTEXEC if you did not specify any configuration files at development/deployment time?
No, but let's say for argument sake that you specified a config file "Config1" at design time. When executed, the package will still look for and use that config file...even if you have specified a config file with the same name ("Config1") in the DTEXEC command.
This is significant because the locations and contents of those 2 files could be different, even if they have the same name. If both are the same file, then the addition in the DTEXEC command is redundant.
Also remember that configurations are applied in the order in which they were added/referenced in the package. This could be significant.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply