May 15, 2012 at 1:16 pm
We have numerous SSIS packages that have Oracle passwords embedded in the connection objects of the SSIS package which is a nightmare for maintenance. Is there any way to keep a centralized password, encrypted , so that the connection objects can access this at run time?
May 15, 2012 at 2:36 pm
You can centralize the password for use by multiple packages using Package Configurations. As far as I know though there is no built-in functionality that will allow SSIS to access encrypted data stored outside the package, such as in an XML Package Configuration file.
You could consider using a Package Configuration where the information is stored in a SQL Server table. If the package ran under a Windows Account you could limit access to the parameter table to that security account and sysadmins only. This will allow you to leverage the SQL Server security model to protect the data which is better than nothing, but the information will not be encrypted.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply