On Dec 3, 10:22 pm, Yuri Bulgakov <yuri.... (AT) gmail (DOT) com> wrote:
Hi Yuri,

I would recommend using Package Configurations to set your
connections, and also setting the ProtectionLevel of all packages to
"ServerStorage" if you are deploying to MSDB (which I would
recommend). I usually use a configuration database to store
configuration details (along with other useful things like precedence
tables, logs, etc). Each package will have a connection to this
database. This is configured using a package configuration that reads
the connection info from an environment variable on the server (I use
Integrated Security and just make sure that the service account has
access to this db). The connection(s) to actual data sources/
destinations are stored in a configuration table in the configuration
database (encrypted if necessary). As package configurations are
applied in order, as long as the configuration database configuration
(say that 10 times while drunk!) is first on the list the other
configurations should retrieve the correct info from the configuration
table.

Hope this helps!
J

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***

I had this same issue with SSIS in 2005. Had nothing to do with the
ProtectionLevel setting.

I had changed the name of the Source and Destination connections to be
more meaningful than the SSIS IMport?Export wizard default names. It
appeared to work as the new connection names did appear in the Source
objects on the data flow task, but I had to open each one and select the
conneciton manager object name again and then select the table and/or re
enter the query. Everything was then fine.

So it appeared the renaming of the connection manager object worked but
it really did not and the connection on the source data flow objects had
to be reaccomplished.





*** Sent via Developersdex http://www.developersdex.com ***