Article ID: 906562 - View products that this article applies to.
Microsoft SQL Server 2005 Integration Services (SSIS) implements security on the client computer and on the server computer when you deploy SSIS packages. You can encrypt the packages to keep the packages' property values secret by setting the protection level of the packages. Packages include the ProtectionLevel property. You can set the ProtectionLevel property according to the level of protection that a package requires.
For example, in a team development environment, a package can be encrypted by using a password that is known to the team members who work on the package. You can easily set a password by using SQL Server Business Intelligence Development Studio or by using the dtutil utility (Dtutil.exe) for a single package. However, if you have to handle lots of packages, the best method is to use the dtutil utility to set the protection level of a batch of SSIS packages. You can generally put a list of individual commands for each package in a .bat file or in a .cmd file and then run the file. If the packages are stored in the same folder, you can use short commands to loop the batch of packages in that folder.
Consider the following scenario:
For more information, type the following command at a command prompt:
Collapse this tableExpand this table
dtutil /? EncryptWhen the other team members receive these packages, the team members may have to change the password to a password that only the team members know or change the protection level. The team members can use the following command to use the dtutil utility to change the password for these packages.
For more information about how to use the dtutil utility to set the protection level of SSIS packages, see the following topics in SQL Server 2005 Books Online:
Article ID: 906562 - Last Review: March 11, 2006 - Revision: 2.2
Contact us for more help