As
part of the package information, some sensitive information like
connection stings, user ids, passwords, etc. are stored to execute the
package. To protect this sensitive information, SSIS provides a mechanism
to encrypt the data. If you have some variables which contain sensitive
information you can set the Sensitive property of that variable to TRUE to
include them for encryption. You can set different level of protection
using a package property called ProtectionLevel.
EncryptSensitiveWithUserKey - Encrypts
sensitive information with the user/developer profile and is the default
protection level.
EncryptSensitiveWithPassword - Encrypts
sensitive information with a password, you will need to provide a
password during development for encryption and decryption of the
sensitive information. When you or someone else opens/runs the package,
she/he needs to provide the same password again for decryption.
EncryptAllWithUserKey - Encrypts all
information (including sensitive) with the user/developer profile.
EncryptAllWithPassword - Encrypts all
information (including sensitive) with a password, you will need to
provide password during development for encryption and decryption of
these sensitive information. When you or someone else opens/runs the
package, she/he needs to provide the same password again for decryption.
DontSaveSensitive - It instructs SSIS to not
store the sensitive information inside the package and let user provide
them again when they are opening/executing it again.
ServerStorage - Protects the whole package
using SQL Server database roles and this protection level is only
applicable if you are storing the package in the msdb database.
No comments :
Post a Comment