Hello,
I'm struggling with an issue on Execute Package Task in SSIS (SQL Server 2008R2)
The context is the following: I'm trying to execute a package stored in SQL Server MSDB table from a "Master" package. We have different environments (DEBUG, DEV, PROD, ...), each of them can execute different builds of the same package (while v3 is still under development in DEV, PROD executes v2, ...)
Which means that the connection used by my "Master" package is dynamically changed to reference the right SQL Server instance (and so MSDB database), depending on the current environment of execution.
My issue is the following: after several tests, I'm pretty sure that the Execute Package Task doesn't used the newly configured connection, but instead keeps the value which is stored in the package (meaning the one used while developing the package).
To change the connection property, I set the value of variable within a script task, and this variable is then used to set the value of the ServerName property of my MSDB connection through an expression.
I actually figured out this issue when I saw in my log table in PROD that it was the build number matching my DEV package that was incorrectly executed on my PROD environment, and the errors where matching some new developments i just did.
Has anyone ever faced such issue?
I can send you a test project which reproduce the error if needed.