Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

SQL Server destination connection manager does not retain values

$
0
0

I have had this over and over again and I am sure many others have, too. I try to use an SSIS package as a template with connection managers from a sample database. The package works fine as is. When I try to convert it to use another database, I put the new server name, user name, password, and select a database. I test the connection and everything is fine. All other components, expressions, and variables are fully converted to the new database. All data destination components are converted over to use the new table. I save the package. There is no evidence whatsoever from any GUI, Dialog box, or property that I can see that has the old connection information. Then I run the package, end up with a login timeout error, and look at my connection manager. ALL the old values are back as if I never changed anything. What am I missing here? It seems as it is useless to create a template. When I try to reconfigure one, it is all lost.

All I really want to do is adapt the same package to import different CSV files into their matching tables. Just change the file connections and sources, and change the destinations and their connectors. Any help will be vastly appreciated.


Viewing all articles
Browse latest Browse all 24688

Trending Articles