I just started developing a package in SSIS 2005 and I have it working (sort of) but I am trying to get it to work using package configurations. Between errors encountered between ProtectionLevels and Configurations, I've been going around in circles. I
would really like some detailed clarifications and hopefully solutions to the issues I'm having now.
I have a package with a single "Execute Sql" task which for the purposes of discussion uses a connection manager 'CONN_ADO' which happens to be an ADO.Net connection. The task has defined variables etc, but the only configurable value for this task is the
ConnectionString and I opted to store it in my Sql Server DB called MAINDB via package configurations. In order to add this configuration to Sql Server, I had to first create an OLEDB connection to MAINDB called CONN_OLEDB. Using this connection, I was able
to create an SSIS Configurations table in MAINDB and store the connectionstring property for CONN_ADO. I made sure the configured value for CONN_ADO in the SSIS configurations table has the password specified in it and the package works perfectly fine under
this setup when the ProtectionLevel is at its default , EncryptSensitiveWithUserKey.
Of course, that was too easy..The default protectionlevel was less than ideal in an actual development environment so I changed the Protection
View Complete Post