Loading Data with Destinations
After a Integration Services package contains a Data Flow task, you can begin to create the package data flow. Integration Services includes three types of data flow components: sources, transformations, and destinations.
The following diagram shows a simple data flow with a source, two transformations, and a destination.
.gif "Data flow")
You use the destinations to load data into files and databases and provide data to other processes. For example, the DataReader destination can provide data for a Reporting Services report. A data flow can include multiple destinations that load data into different data stores. For more information, see Integration Services Destinations.
You can also write custom destinations. For more information, see Developing a Custom Data Flow Component and Developing Specific Types of Data Flow Components.
After you add the source to the data flow designer and configure the source, you can add the destination to the data flow designer. Before you finish configuring the destination, you must connect the destination to the data flow by connecting the output of another transformation or source in the data flow to the input of the destination. The connector between two data flow components is called a path. For more information about connecting components and working with paths, see Connecting Components with Paths.
To add and configure a destination when creating a package
Use either the SQL Server Import and Export Wizard or Integration Services Connection Project Wizard.
In addition to creating and configuring a destination, these wizards also help you create and configure data sources, and the connection managers that are used by the sources and destinations. For more information, see Creating a Package by Running a Wizard.
To add a destination to an existing data flow
To connect a destination to a data flow
To set the properties of a destination
|
.gif "Integration Services icon (small)")
Stay Up to Date with Integration Services