Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Hands-On Microsoft SQL Server 2008 Integration Services part 70. 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. . | 668 Hands-On Microsoft SQL Server 2008 Integration Services plan represents the outputs of asynchronous transformations. The path plan creates a plan for each execution plan or subplan. Actually the pipeline uses two different types of threads SourceThreads and WorkThreads. The SourceThreads are directly related to the output plans that represent the data flow sources and the asynchronous transformations outputs. On the other hand WorkThreads are related to the path plans that represent the execution paths and subpaths. Each source thread has to create a buffer and call the PrimeOutput method on the source component or the component with asynchronous output so that it can start filling up the output buffer with the data rows. This is where the execution starts and the rest of the work is distributed among WorkThreads. The WorkThreads are also linked to the data flow task property called EngineThreads. Refer to earlier Figure 15-3 which shows the EngineThreads property set to the default value of 10. This EngineThreads property value suggests to the data flow engine the number of threads to use during execution. You will study more about the EngineThreads property later in this chapter. 15. Next search for the string BufferSizeTuning and read through the messages related to the BufferSizeTuning event. Here is one example Rows in buffer type 2 would cause a buffer size greater than the configured maximum. There will be only 2449 rows in buffers of this type. This event indicates that the buffer size created will be larger than the default size configured it also tells you the number of rows that this buffer will be able to hold. 16. Finally look through the PipelineInitialization log entries which tell you about temporary BLOB and buffer storage locations for the pipeline execution environment. Review This exercise showed you that the pipeline engine divides the pipeline work in discrete execution paths on the basis of synchronicity in the package. Whenever it comes
