May 25, 2010 at 12:02 am
Hi
We have a module which is built on SSIS. When executing the package, the connection string needs to be given always which is tiresome.
Say i have built on connectionA and deployed the package to server.
Now requirement is to connect to different server, so i just change the connection string to serverB, uid and password.
This is quite frequently done in our environment for testing purpose.
is there ant way that the updating the connection string is not always required and it picks up right uid and pwd
May 25, 2010 at 8:08 am
It sounds like you need to keep your connection string in a Package Configuration and not inside the package itself. Package configurations can be stored either as files or in a database table. Since they would contain your user ids and passwords, you would want to restrict access to their locations. You may be able to encrypt them, but I do not know how to do that.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply