Anyone familiar with Package Protection Levels?

Question

Anyone familiar with Package Protection Levels?

chris-1111548

Valued Member

Points: 63
More actions
September 22, 2009 at 4:48 am

#134012

Clients send us data in CSV and Excel files every day, each client's data file has a different structure to the rest.
We have created 70+ SSIS Packages which are run each morning to import the clients' data.
If the package are run on the same PC as last time, then all is fine. However if the project is opened and the packages are run on a different PC then the new user has to key in the password for the server database for each package run.
Then, of course, the next time a different PC (or even the initial PC) is used to run a package then the server database password has to be re-keyed again.
There are 6 options for ProtectionLevel:
*DonSaveSensitive - doesn't save any connection passwords
*EncryptSensitiveWithPassword - saves the connection passwords, but the package itself is passworded. So kind of defeats the purpose.
*EncryptAllWithPassword - same as above
*EncryptSensitiveWithUserkey - saves password, but only the user who last saved it can run the package, otherwise password needs to be re-entered.
*EncryptAllWithUserKey - same as above.
*ServerStorage - only usable if packages are stored in database.
What I need is to be able to save the password, but with no encryption to the package at all - not passworded or userkey.
This is so anyone can open the package and run it, without having to key in any passwords.
I just need an option that is *SaveSensitive, but it doesn't seem to exist.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Henrico Bekker One Orange Chip Points: 27652 More actions · Answer 1

(Please correct me if I am wrong) but I am almost sure those are the only options, I have Server Storage as a option as well, but doubt if it will help you..

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

COZYROC One Orange Chip Points: 28499 More actions · Answer 2

chris-1111548 (9/22/2009)
Clients send us data in CSV and Excel files every day, each client's data file has a different structure to the rest.
We have created 70+ SSIS Packages which are run each morning to import the clients' data.
If the package are run on the same PC as last time, then all is fine. However if the project is opened and the packages are run on a different PC then the new user has to key in the password for the server database for each package run.
Then, of course, the next time a different PC (or even the initial PC) is used to run a package then the server database password has to be re-keyed again.
There are 6 options for ProtectionLevel:
*DonSaveSensitive - doesn't save any connection passwords
*EncryptSensitiveWithPassword - saves the connection passwords, but the package itself is passworded. So kind of defeats the purpose.
*EncryptAllWithPassword - same as above
*EncryptSensitiveWithUserkey - saves password, but only the user who last saved it can run the package, otherwise password needs to be re-entered.
*EncryptAllWithUserKey - same as above.
*ServerStorage - only usable if packages are stored in database.
What I need is to be able to save the password, but with no encryption to the package at all - not passworded or userkey.
This is so anyone can open the package and run it, without having to key in any passwords.
I just need an option that is *SaveSensitive, but it doesn't seem to exist.

What you can do is use the DonSaveSensitive option and then provide the credentials with common configuration file or table from outside.

---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/