tailieunhanh - Hands-On Microsoft SQL Server 2008 Integration Services part 30

Hands-On Microsoft SQL Server 2008 Integration Services part 30. Deploy and manage high-performance data transformation solutions across your enterprise using the step-by-step techniques in this fully revised guide. Hands-On Microsoft SQL Server 2008 Integration Services, Second Edition explains the tools and methods necessary to extract conclusive business intelligence from disparate corporate data. Learn how to build and secure packages, load and cleanse data, establish workflow, and optimize performance. Real-world examples, detailed illustrations, and hands-on exercises are included throughout this practical resource. . | This page intentionally left blank Chapter 7 Securing Integration Services Packages In This Chapter Digitally Signing the Package Excluding Sensitive Information from the Package Encrypting Sensitive Information in the Package Encrypting All the Information in the Package Using Integration Services Fixed Database-Level Roles Considerations for Different Storage Areas Summary 270 Hands-On Microsoft SQL Server 2008 Integration Services Security in SQL Server 2008 Integration Services has been enhanced a great deal compared to DTS 2000. DTS uses package password protection SQL Server Security and SQL Server Agent service security while Integration Services provides the features used by DTS and a lot more to enhance data security. SSIS provides the ability to secure data and connections from various perspectives depending upon the situation. By design Integration Services will communicate with SQL Server only over an encrypted channel to protect sensitive data. In Integration Services the sensitive information means the passwords used in connection strings any property of the custom-built components that has the sensitive attribute set or any variable tagged with the sensitive attribute. Integration Services secures your packages and data by providing the facilities to do the following Digitally sign the package. Exclude sensitive information from the package. Encrypt sensitive information in the package. Encrypt all the contents of the package. Control access to the package by using database-level roles. Secure storage areas. Let s take a detailed look at these options and what they offer in terms of securing Integration Services packages and the metadata used in them. Digitally Signing the Package Development of a complex Integration Services solution involves several developers who create many smaller packages to join as modules and form a complex solution for the business problem. During development phase a package that has been tested successfully to perform a .