Select an existing connection manager from the list, or create a new connection by clicking 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..
Create a new table or view by using the Create Table dialog box.
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 results by using the Preview Query Results dialog box. Preview can display up to 200 rows.
You can use the .NET Data Provider for SQL Server (SqlClient) to connect to Microsoft Windows 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).
If a SQL Server or Sybase source table includes an identity column, you must use Execute SQL tasks to run a SET IDENTITY_INSERT statement before and after the ADO NET destination. The identity column property specifies an incremental value for the column. The SET IDENTITY_INSERT statement enables explicit values to be inserted into the identity column. To run the CREATE TABLE and SET IDENTITY statements on the same database connection, set the RetainSameConnection property of the ADO.NET connection manager to True. Also, use the same ADO.NET connection manager for the Execute SQL tasks and the ADO NET destination.