Shulou(Shulou.com)06/02 Report--

This article mainly introduces "how to troubleshoot ADO.NET connection manager". In daily operation, I believe many people have doubts about how to troubleshoot ADO.NET connection manager. Xiaobian consulted all kinds of information and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubt of "how to troubleshoot ADO.NET connection manager". Next, please follow the editor to study!

The ADO.NET connection manager enables packages to access data sources using the .NET provider. This connection manager is typically used to access data sources such as Microsoft SQL Server, as well as data sources exposed through OLE DB and XML in custom tasks written in managed code in languages such as 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 its properties, and adds the connection manager to the package's Connections collection. 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 used by the connection manager.

You can configure the ADO.NET connection manager by providing a specific connection string that is configured to meet the requirements of the selected .NET provider. Includes the name of the data source to connect to (depending on the provider). Provide the appropriate security credentials for the selected provider. Indicates whether connections created from the connection manager are retained at run time. Many of the configuration options for the ADO.NET connection manager depend on the .NET provider that the connection manager uses.

Troubleshooting ADO.NET connection Manager

You can record calls made by the ADO.NET connection manager to the external data provider. Using this logging feature, you can troubleshoot ADO.NET connection manager connections to external data sources. To log calls made by the ADO.NET connection manager to the external data provider, enable package logging at the package level and select the Diagnostic event. For more information, see package troubleshooting.

When the ADO.NET connection manager reads data, data of some SQL Server date data types produces the results shown in the following table. Unless the package uses the parameterized SQL command, the package will fail. To use the parameterized SQL command, use the execute SQL task in the package. For more information, see executing SQL tasks and using parameters and return codes in SQL tasks.

ADO.NET connection Manager truncated millisecond valu

Ms141676.note (zh-cn,SQL.100) .gif Note: for more information about SQL Server data types and how these data types map to Integration Services data types, see data types (Transact-SQL) and Integration Services data types.

Configure ADO.NET connection Manager

Properties can be set through the SSIS designer or programmatically. For more information about the properties that can be set in the SSIS designer, click one of the following topics: configure ADO.NET connection Manager connection Manager Dialog Box (Analysis Services-Multidimensional data) for information about configuring the connection manager programmatically, see ConnectionManager and adding connections programmatically.

At this point, the study on "how to troubleshoot the ADO.NET connection manager" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.