ADO NET Destination

The ADO NET destination loads data into a variety of ADO.NET-compliant databases that use a database table or view. You have the option of loading this data into an existing table or view, or you can create a new table and load the data into the new table.

You can use the ADO NET destination to connect to Microsoft Azure SQL Database. Connecting to SQL Database by using OLE DB is not supported. For more information about SQL Database, see General Guidelines and Limitations (Windows Azure SQL Database).

Troubleshooting the ADO NET Destination

You can log the calls that the ADO NET destination makes to external data providers. You can use this logging capability to troubleshoot the saving of data to external data sources that the ADO NET destination performs. To log the calls that the ADO NET destination makes to external data providers, enable package logging and select the Diagnostic event at the package level. For more information, see Troubleshooting Tools for Package Execution.

Configuring the ADO NET Destination

This destination uses an ADO.NET connection manager to connect to a data source and the connection manager specifies the ADO.NET provider to use. For more information, see ADO.NET Connection Manager.

An ADO NET destination includes mappings between input columns and columns in the destination data source. You do not have to map input columns to all destination columns. However, the properties of some destination columns can require the mapping of input columns. Otherwise, errors might occur. For example, if a destination column does not allow for null values, you must map an input column to that destination column. In addition, the data types of mapped columns must be compatible. For example, you cannot map an input column with a string data type to a destination column with a numeric data type if the ADO.NET provider does not support this mapping.

Note

SQL Server does not support inserting text into columns whose data type is set to image. For more information about SQL Server data types, see Data Types (Transact-SQL).

Note

The ADO NET destination does not support mapping an input column whose type is set to DT_DBTIME to a database column whose type is set to datetime. For more information about Integration Services data types, see Integration Services Data Types.

The ADO NET destination has one regular input and one error output.

You can set properties through SSIS Designer or programmatically.

The Advanced Editor dialog box reflects the properties that can be set programmatically. For more information about the properties that you can set in the Advanced Editor dialog box or programmatically, click one of the following topics:

ADO NET Destination Editor (Connection Manager Page)

Use the Connection Manager page of the ADO NET Destination Editor dialog box to select the ADO.NET connection for the destination. This page also lets you select a table or view from the database.

To open the Connection Manager page

  1. In SQL Server Data Tools (SSDT), open the Integration Services package that has the ADO NET destination.

  2. On the Data Flow tab, double-click the ADO NET destination.

  3. In the ADO NET Destination Editor, click Connection Manager.

Static Options

Connection manager
Select an existing connection manager from the list, or create a new connection by clicking New.

New
Create a new connection manager by using the Configure ADO.NET Connection Manager dialog box.

Use a table or view
Select an existing table or view from the list, or create a new table by clicking New..

New
Create a new table or view by using the Create Table dialog box.

Note

When you click New, Integration Services generates a default CREATE TABLE statement based on the connected data source. This default CREATE TABLE statement will not include the FILESTREAM attribute even if the source table includes a column with the FILESTREAM attribute declared. To run an Integration Services component with the FILESTREAM attribute, first implement FILESTREAM storage on the destination database. Then, add the FILESTREAM attribute to the CREATE TABLE statement in the Create Table dialog box. For more information, see Binary Large Object (Blob) Data (SQL Server).

Preview
Preview results by using the Preview Query Results dialog box. Preview can display up to 200 rows.

Use bulk insert when available
Specify whether to use the SqlBulkCopy interface to improve the performance of bulk insert operations.

Only ADO.NET providers that return a SqlConnection object support the use of the SqlBulkCopy interface. The .NET Data Provider for SQL Server (SqlClient) returns a SqlConnection object, and a custom provider may return a SqlConnection object.

You can use the .NET Data Provider for SQL Server (SqlClient) to connect to Microsoft Azure SQL Database.

If you select Use bulk insert when available, and set the Error option to Redirect the row, the batch of data that the destination redirects to the error output may include good rows.For more information about handling errors in bulk operations, see Error Handling in Data. For more information about the Error option, see ADO NET Destination Editor (Error Output Page).

Note

If a SQL Server or Sybase source table includes an identity column, you must use Execute SQL tasks to enable IDENTITY_INSERT before the ADO NET destination and to disable it again afterward. (The identity column property specifies an incremental value for the column. The SET IDENTITY_INSERT statement lets explicit values from the source table be inserted into the identity column in the destination table.)

To run the SET IDENTITY_INSERT statements and the data loading successfully, you have to do the following things.

  1. Use the same ADO.NET connection manager for the Execute SQL tasks and for the ADO.NET destination.
  2. On the connection manager, set the RetainSameConnection property and the MultipleActiveResultSets property to True.
  3. On the ADO.NET destination, set the UseBulkInsertWhenPossible property to False.

    For more information, see SET IDENTITY_INSERT (Transact-SQL) and IDENTITY (Property) (Transact-SQL).

External Resources

Technical article, Loading data to Windows Azure SQL Database the fast way, on sqlcat.com

ADO NET Destination Editor (Mappings Page)

Use the Mappings page of the ADO NET Destination Editor dialog box to map input columns to destination columns.

To open the Mappings page

  1. In SQL Server Data Tools (SSDT), open the Integration Services package that has the ADO NET destination.

  2. On the Data Flow tab, double-click the ADO NET destination.

  3. In the ADO NET Destination Editor, click Mappings.

Options

Available Input Columns
View the list of available input columns. Use a drag-and-drop operation to map available input columns in the table to destination columns.

Available Destination Columns
View the list of available destination columns. Use a drag-and-drop operation to map available destination columns in the table to input columns.

Input Column
View the input columns that you selected. You can remove mappings by selecting <ignore> to exclude columns from the output.

Destination Column
View each available destination column, regardless of whether it is mapped or not.

ADO NET Destination Editor (Error Output Page)

Use the Error Output page of the ADO NET Destination Editor dialog box to specify error handling options.

To open the Error Output page

  1. In SQL Server Data Tools (SSDT), open the Integration Services package that has the ADO NET destination.

  2. On the Data Flow tab, double-click the ADO NET destination.

  3. In the ADO NET Destination Editor, click Error Output.

Options

Input or Output
View the name of the input.

Column
Not used.

Error
Specify what should happen when an error occurs: ignore the failure, redirect the row, or fail the component.

Related Topics: Error Handling in Data

Truncation
Not used.

Description
View the description of the operation.

Set this value to selected cells
Specify what should happen to all the selected cells when an error or truncation occurs: ignore the failure, redirect the row, or fail the component.

Apply
Apply the error handling option to the selected cells.