Database Reference
In-Depth Information
As each task executes, the task displays a yellow wheel and then either a red
X
or green check mark (Figure
7-34
). The yellow status means that the underlying code within the task is currently running in the debugging
engine. When the task icon turns green, it means that all the code has stopped running and that the execution of
that code was successful. When the task icon turns red, it means that the execution of the code was unsuccessful.
No matter the outcome, the debugging engine does not automatically shut down but instead continues
running in the background. This is evidenced by the word
(Running)
within parentheses being displayed at the
top of the Visual Studio window (Figure
7-34
).
Figure 7-34.
A task changes color to indicate its status as it is running
You cannot edit the SSIS package while the debugger is running. Therefore, once all of the tasks have
completed, stop the debugger by selecting the hyperlinked message that we circled in Figure
7-34
or by selecting
the Stop Debugging option from the Visual Studio Debug menu. Once the SSIS code stops running, you can
continue to edit your SSIS package.
You may have noticed that there is an indicator on the sequence container as well as the individual tasks
(Figure
7-34
). You can debug more than one task at a time within Visual Studio, either by executing the SSIS
package file as a whole or by executing all of the tasks within a sequence container.
To execute a set of tasks within a sequence container, right-click the container and choose Execute
Container from the context menu. To execute all the tasks within a particular SSIS package, select the package file
in Solution Explorer, right-click it, and then choose Execute Package from the context menu, as shown in Figure
7-35
.
Executing individual tasks as you configure them allows you to test and troubleshoot errors immediately. If
you have a collection of tasks that must work together, you will want to test them collectively as well.
