Database Reference
In-Depth Information
Figure 8-11.
The Data Flow Path Editor window
If you try to connect the arrows before the source component is configured, there will be no metadata to
pass on to the destination component. This causes errors that are tedious to resolve—not difficult, just tedious.
We recommend avoiding this practice and connecting the arrows only after properly configuring each beginning-
point component. Be sure that you do not open the destination component editor until after the source
component metadata is available.
■
The most common problem we see when working with data flows is connecting the blue or red
arrows during the outlining process. if, for some reason, you connect an arrow between two components before the
source component is configured, simply delete the destination component and try again. it is possible to fix the issue
without deleting components, but most of the time, deleting is the simplest or fastest way to resolve the issue.
Important
Error Outputs Paths
Error flows have the ability to route data to a separate location in case of an error. The error output path arrow
looks similar to the data flow path arrow, but it is red in color, instead of blue (Figure
8-12
). To use this feature,
first add an additional destination component, such as the additional OLE DB destination component shown in
Figure
8-12
, and then connect the error output path arrow to the new destination component. The destination
component will usually be a flat file or a SQL table.
