Integration Services has a variety of tools and provides various techniques you can use to see what a task or package is doing and how it is doing it, as you’ll see in this course. You can cause the behavior or a task to change when problems arise, whether from bad data or missing resources, and you can partition a Control Flow so that a whole separate set of tasks execute only when certain kinds of events occur. You can pause package execution at pre-defined breakpoints—conceptually similar to breakpoints in programming tools but quite different in practice. You cause the package to store information in a checkpoint file about where it failed so that the next time you run the package it doesn’t repeat any tasks that completed successfully. And you can log many kinds of information about the package as each task executes. In this course, you’ll learn about these debugging, error handling, and logging features that can help you diagnose most kinds of problems in your package.
Lesson 1:
Lesson 2:
Lesson 3:
Lesson 4:
Lesson 5:
Lesson 6:
Lesson 7:
Lesson 8: