SQL Server Development Bookmark and Share   
 index > SQL Server Integration Services > Persist ConnectionString
 

Persist ConnectionString

Hello All,

I have changed connection string property of connectionmanger at runtime and saved package.But my new connectionstring is not persisting, i am getting my old connection string after reload package .

ConnectionManager cm = package.Connections[test.ConnectionManagerID];

cm.ConnectionString = @"C:\Test.csv";

app.SaveToDtsServer(package, null,

@"File System\Dupaco Load Next Best.dtsx", "CIRCLE");

How can I save new connection string?.

Please help me.

Thanks

Subin

subin2  Tuesday, April 03, 2007 6:48 AM

The ProtectionLevel property of the ConnectionManager will change what and ifsensitive information is saved.

Personally I do not like saving sensitive information in a package, I much prefer using configurations. This allows you to keep such information externally, and just by changing the configuartion information between environments you can easily manage this. This mechanism is obviously great for when moving packages between test and production environments for example, but it scales right down to the developer's desktop, so you use the same mechanism throughout.

Darren Green SQLIS  Tuesday, April 03, 2007 9:43 AM

The ProtectionLevel property of the ConnectionManager will change what and ifsensitive information is saved.

Personally I do not like saving sensitive information in a package, I much prefer using configurations. This allows you to keep such information externally, and just by changing the configuartion information between environments you can easily manage this. This mechanism is obviously great for when moving packages between test and production environments for example, but it scales right down to the developer's desktop, so you use the same mechanism throughout.

Darren Green SQLIS  Tuesday, April 03, 2007 9:43 AM

You can use google to search for other answers

Custom Search

More Threads

• Can we save SSIS package as VB.net code (like in DTS)
• file could not be opened in bulk insert task
• Funny error during runs
• Cannot Run SSIS Package in Job Agent
• problem with xml source
• FTP - SSIS vs DTS
• [SSIS 2005] : parsing ISBN number from a XML source
• Transactions and Create Table statements
• Timeout error when executing SQL command from the Script Task
• Fuzzy Lookup Error