March 28, 2008 at 8:34 am
I am wondering what is the best way to managed and control SSIS packages. In our SSIS packages, we have to provide a password for some of the Connection Managers. The problem arises when the creator (say Bob) of the package is unavailable and someone else (Fred) needs to make changes. When this occurs, if Fred edits the package it loses its password AND it will no longer let the password be saved. Bob needs to go back in and save the password.
My thought is to create a "production login" on the server and do all administration of SSIS packages from that login. Thus the login could be shared amongst those that need to access the packages. (The access would be heavily controlled.)
Is this a good methodology? Is there a better way?
Any suggestions would be much appreciated.
Rob
March 28, 2008 at 9:32 am
If you set your packages to DontSaveSensitive the package will not store the passwords, but you can use package configurations to store the connection passwords.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply