Hi all
I am sure I am not the only one who have seen this before:
At some point, configuration values stored in sql server (2008 r2) table, stop effecting target variables in ssis package.
Instaed saved values in the package seem to be in effect then(this is apparent by adding breakpoints and watching variables at run time).
Then out of the blue values from configuration table is reflected in the package again
(without changing any thing in the deffenitions of that configuration...)
Any possible reasons?? I have sql server 2008 r1 installed together with 2008 r2 client.
Perhaps this can be a reason for communication instability between sql server and client applications???
TIA
Rea