4.3. Destinations
Inside the data flow, destinations accept the data from the data sources and from the transformations. The architecture can send the data to nearly any OLE DB–compliant data source, a flat file, or Analysis Services. Like sources, destinations are managed through the Connection Manager. The configuration difference between sources and destinations is that in destinations, you have a Mappings page (shown in Figure 4-11), where you specify how the inputted data from the data flow maps to the destination.
Figure 4.11. Figure 4-11
You won't be able to configure the destination until it is connected to the data flow. To do this, select the source or a transformation and drag the green arrow to the destination. If you want to output the bad data to a destination, you would drag the red arrow to that destination. If you try to configure the destination before attaching it to the transformation or source, you would see the error in Figure 4-12.
Figure 4.12. Figure 4-12
4.3.1. Data Mining Model Training
The Data Mining Model Training destination can train an Analysis Services data mining model by passing it data from the data flow. You can train multiple mining models from a single destination and data flow. To use this destination, you would select an Analysis Services ...
Get Professional SQL Server™ 2005 Integration Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.