SSIS - Package Protection Level

SSIS Package Protection Level property tells SSIS how to handle sensitive information stored within SSIS packages. If we don't set the ProtectionLevel correctly, the package may become unusable.

1. DontSaveSensitive
   
   When the package is saved, sensitive values will be removed. This will result in passwords needing to be supplied to the package, through a configuration file or by the user.
   
2. EncryptSensitiveWithUserKey
   
   This will encrypt all sensitive data on the package with a key based on the current user profile. This sensitive data can only be opened by the user that saved it. It another user opens the package, all sensitive information will be replaced with blanks. This is often a problem when a package is sent to another user to work on.
   
3. EncryptSensitiveWithPassword
   
   Sensitive data will be saved in the package and encrypted with a supplied password. Every time the package is opened in the designer, you will need to supply the password in order to retrieve the sensitive information. If you cancel the password prompt, you will be able to open the package but all sensitive data will be replaced with blanks. This works well if a package will be edited by multiple users.
   
4. EncryptAllWithPassword
   
   This works the same as EncryptSensitiveWithPassword except that the whole package will be encrypted with the supplied password. When opening the package in the designer, you will need to specify the password or you won’t be able to view any part of the package.
   
5. EncryptAllWithUserKey
   
   This works the same as EncryptSensitiveWithUserKey except that the whole package will be encrypted. Only the user that created the package will be allowed to open the package.
   
6. ServerStorage
   
   This option will use SQL Server database roles to encrypt information. This will only work if the package is saved to an SSIS server for execution.