Dela via


ADO.NET Connection Manager

An ADO.NET connection manager enables a package to access data sources by using a .NET provider. This connection manager is typically used to access data sources such as Microsoft SQL Server, and also data sources exposed through OLE DB and XML in custom tasks that are written in managed code by using a language such C#.

When you add an ADO.NET connection manager to a package, SQL Server Integration Services creates a connection manager that is resolved as an ADO.NET connection at run time, sets the connection manager properties, and adds the connection manager to the Connections collection on the package.

The ConnectionManagerType property of the connection manager is set to ADO.NET. The value of ConnectionManagerType is qualified to include the name of the .NET provider that the connection manager uses.

You can configure an ADO.NET connection manager in the following ways:

  • Provide a specific connection string configured to meet the requirements of the selected .NET provider.

  • Depending on the provider, include the name of the data source to connect to.

  • Provide security credentials as appropriate for the selected provider.

  • Indicate whether the connection that is created from the connection manager is retained at run time.

Many of configuration options of the ADO.NET connection manager depend on the .NET provider that the connection manager uses.

Troubleshooting the ADO.NET Connection Manager

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

When being read by an ADO.NET connection manager, data of certain SQL Server date data types will generate the results shown in the following table.

SQL Server data type

Result

time, datetimeoffset

The package fails unless the package uses parameterized SQL commands. To use parameterized SQL commands, use the Execute SQL Task in your package. For more information, see SSIS Execute SQL Task and Working with Parameters and Return Codes in the Execute SQL Task.

datetime2

The ADO.NET connection manager truncates the millisecond value.

Note

For more information about SQL Server data types and how they map to Integration Services data types, see Data Types (Transact-SQL) and Integration Services Data Types.

Configuring the ADO.NET Connection Manager

You can set properties through SSIS Designer or programmatically.

For more information about the properties that you can set in SSIS Designer, click one of the following topics:

For information about configuring a connection manager programmatically, see ConnectionManager and Adding Connections Programmatically.

Integration Services icon (small) Stay Up to Date with Integration Services

For the latest downloads, articles, samples, and videos from Microsoft, as well as selected solutions from the community, visit the Integration Services page on MSDN or TechNet:

For automatic notification of these updates, subscribe to the RSS feeds available on the page.