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

Hands-On Microsoft SQL Server 2008 Integration Services part 32. 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. . | 288 Hands-On Microsoft SQL Server 2008 Integration Services Figure 7-7 Assigning a Reader role to the Team role assign a writer role to user accounts or groups. In the last part you assigned the Reader role directly to the user-defined role and then linked that role to a fixed database-level role. Alternatively you could have added users directly to the fixed database-level role though that would not be a recommended approach. Whichever way you choose to go make sure you assign a reader or writer role to the user or user-defined role and link them to the fixed database-level roles. Another point worth mentioning here is that any metadata or configuration files that are saved outside the package cannot be protected solely by the database-level roles. Carefully consider where you want to store your configuration files or other miscellaneous files so that they are properly protected. Examples of such files that can be saved outside the package are configuration files checkpoint files cache files or log files. If you are saving these files to SQL Server but outside the package or to the file system you need to secure them with appropriate security measures. For more details on this refer to the next section. Last but not least you also need to assign permissions to user-defined roles on the objects such as tables views and so on being accessed by your package otherwise the package will run but will fail for not being able to access the objects. Considerations for Different Storage Areas You need to protect the Integration Services packages and the package metadata from unauthorized access or hardware failures. Integration Services packages may have associated configuration files that have been saved outside the package. Chapter 7 Securing Integration Services Packages 289 These configuration files are used to update values of properties at run time making it easier to deploy packages from a development environment to a production environment. While both the package and