Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

ADO.NET Connection Manager

Updated: 12 December 2006

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 2005, 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 2005 Integration Services (SSIS) 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.

Starting in Microsoft SQL Server 2005 Service Pack 2 (SP2), you are able to log the calls that the ADO.NET connection manager makes to external data providers. You can use this new 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 an external data provider, enable package logging and select the Diagnostic event at the package level. For more information, see Troubleshooting Package Execution.

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.

Release History

12 December 2006

New content:
  • Added information about how SQL Server 2005 SP2 includes new logging messages that enable users to troubleshoot the calls that the connection manager makes to external data providers.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft