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

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 40. 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. . | 368 Hands-On Microsoft SQL Server 2008 Integration Services did in the control flow drag the output of a data flow component and drop it onto the input of the next component and the line formed connecting the data flow components on the Data Flow Designer surface is called the dataflow path. They may look similar on the Designer but there are major differences between a precedence constraint and a data flow path as both represent different functionalities in their own right. Note that the data flow path line is thinner than the precedence constraint line and can be either green or red depending on whether it is representing Output Path or Error Output Path. In the Control Flow when you connect a task to another using a precedence constraint and click the task again you will see another green arrow indicating that you can configure multiple precedence constraints for the tasks However in the data flow the data flow paths are limited to the number of outputs and error outputs available to the source component. There s another important difference the data flow path actually simulates a pipe connecting the pipeline components in the data flow path remember that dataflow is also known as pipeline through which data flows whereas a precedence constraint specifies a condition when the next task can be executed in the workflow. When you click a component for example OLE DB source in the Data Flow Designer surface depending upon the outputs available from the component you may see a combination of green and red arrows. Some components have both output and error output paths some have only one and some have no output such as destinations. Our example component OLE DB source has both output and error output available and hence shows both green and red arrows. After you connect a component to another component using a data flow path on the Data Flow Designer you can configure the properties of the data flow path using Data Flow Path Editor. This editor can be opened by .