Đang chuẩn bị liên kết để tải về tài liệu:
Hands-On Microsoft SQL Server 2008 Integration Services part 22

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Hands-On Microsoft SQL Server 2008 Integration Services part 22. 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. . | 188 Hands-On Microsoft SQL Server 2008 Integration Services package and run that as a child package using the Execute Package task in the main SSIS package and hence avoid access to salaries data. Probably the biggest benefit of having an Execute Package task is that the packages are able to communicate with other packages and have an effect on the success or failure of other packages. To clarify consider the container hierarchy in which errors and events get flagged up the hierarchy with the package being at the top of the hierarchy. When we use a child package in a parent package the Execute Package task actually contains the child package and becomes a parent container for that child package. Any event occurring in the child package gets passed on to the Execute Package task which it can share with other Execute Package tasks used in the parent package. Now think of transactions that cause tasks to commit or roll back as a unit within a package. Using this task transactions can actually span across packages and can cause multiple packages to commit or roll back as a unit. SSIS provides you the benefits of dealing with individual tasks and lets you use them as an independent unit yet at the same time you are also able to integrate the packages together to work as a unit. You can run a child package in its own process or in the process of the parent package using the ExecuteOutOfProcess option. If you are following a modular design for your package and want your parent and child packages to commit or fail together as a single unit you will be using the in-process method i.e. you will run the child package in the same process as that of the parent package. For this configuration you will not be running additional processing threads and the memory required by the process will of course be less. In this case the context switching will not happen and you will experience less processing overhead. However the down side is that if a child package crashes due to some .