Hands-On Microsoft SQL Server 2008 Integration Services part 67. 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. . | 638 Hands-On Microsoft SQL Server 2008 Integration Services Figure 15-2 Changing variable value at run time using the Watch 1 window Review In this Hands-On exercise you ve seen how the Progress tab shows the number of executions of a task along with other information. This tab also displays alert warning and error messages while the package executes. These messages are still available after the package completes execution when the Progress tab becomes the Execution Results tab. You ve also used the Locals window to see the values of variables that get updated with each iteration of the Foreach Loop container. Then you changed the breakpoint setting and jumped four steps at a time. This feature helps a lot while debugging packages with large data sets and you need to check the multiple points of failure. The most interesting thing you ve learned is how to change the variable value on the fly and inject that value into the package execution. You can easily simulate various values and see how the package responds to these values using this feature. Chapter 15 Troubleshooting and Performance Enhancements 639 Logging Feature The logging feature of Integration Services can be used to debug task failures and monitor performance issues at run time. A properly configured log schema to log run-time events can be an effective tool in your debugging toolkit. Logging has been discussed in detail in Chapter 8 along with a discussion on various log providers. Refer to that chapter for more details on how to configure logging in your package. Precedence Constraints and Data Flow Paths You ve used these two connecting elements in package development so now you understand that precedence constraints are used to connect control flow tasks whereas data flow paths are used to connect data flow components. You can use precedence constraints to control the workflow in a package by configuring the evaluation operation to a constraint or an expression or a combination of both. Using a .
