Datasheet

In this configuration, if there are less than 400 rows transformed, Stub Code 2 will never execute, even
though there’s an On Success precedence constraint between the Data Flow Task and the task. This is
because you have a Logical
And condition on the Stub Task 2 when multiple constraints are connected
into it. This means that both the Data Flow Task and the Stub Code Task must successfully execute before
the Stub Code 2 Task executes. You may also want the Stub Code 2 Task to execute when either task suc-
cessfully completes. To do this, you can double-click either of the precedence constraints that connect to
Stub Code 2 and change the Multiple constraints option to Logical OR.
Package Execution
Notice that after you change the constraint type, the solid green line turns into a dotted green line as
shown in Figure 1-13. At this point, you’re ready to execute the package by right-clicking the package in
the Solution Explorer and clicking Execute Package. If you transformed less the 400 records, the package
will look like Figure 1-13, where the Data Flow and Stub Code 2 executes.
Figure 1-13: Solid line changing to dotted line
One way you can see how many rows transformed is to go to the Data Flow tab before stopping the
package. You’ll see how many rows transformed through the pipeline (shown in Figure 1-14). You can
stop the package by clicking the Stop button (the square blue button on the BIDS toolbar) or by clicking
Stop Debugging from the Debug menu. If you have any problems executing the package, you can go to
the Progress tab to see the error. After you stop the package, the Progress tab turns into the Execution
Results tab, which shows the results of the last package execution.
When you execute a package from the BIDS environment where you can see the results visually, you’re
executing the package in debug mode. You can also execute the package without debugging by selecting
Start Without Debugging from the Debug menu. This performs slightly faster than executing a package
from within debug mode, but it’s much harder to troubleshoot an issue.
Executing a package outside of debug mode opens a command prompt, as shown in Figure 1-15, and
runs the
dtexec.exe utility. You can tell the package successfully executed by the DTSER_SUCCESS code
at the end of the execution. You can also see how fast each task and container executed after each item
completes in the command window, or how fast the entire package executed, which is shown at the bot-
tom of the command line execution output (in the command window).
17
Chapter 1: Getting Started
04_134115 ch01.qxp 4/24/07 6:40 PM Page 17