I have a SSIS package that I execute several times in parallel from different SQL Server Agent Jobs. I set the ConnectionString to the Connection Manager by using the command line parameter /CONNECTION.
It seems that the SSIS is overriding my run-time ConnectionString again with the design-time value. I also found an MSDN article stating that this is indeed what happens.
http://msdn.microsoft.com/en-us/library/bb500430(v=sql.105).aspx
Is there a way to override the Connection Manager ConnectionString during run-time? I need this functionality because I’m using the same packages for different setups so I cannot “hard-code” the ConnectionString.
If you are limited to use command line only, then use /SET to change a value of a variable at runtime and using expressions, build your connection string from that variable (as the link you posted above says /SET overrides design-time value, whereas /CONNECTION doesn’t.)
The other way to override or provide a ConnectionSting during runtime is to start usinng Package Configurations as described here.