Microsoft KB Archive/316757

= BUG: SqlClient connection pooling that uses integrated security is slower than OleDb =

Article ID: 316757

Article Last Modified on 3/9/2006

-

APPLIES TO


 * Microsoft .NET Framework 1.1 Service Pack 1
 * Microsoft ADO.NET 1.1

-



This article was previously published under Q316757



This article refers to the following Microsoft .NET Framework Class Library namespace:
 * System.Data



SYMPTOMS
Microsoft SQL Server .NET data provider (SqlClient) is slower than OLE DB .NET data provider (OleDb) when you use connection pooling with integrated security.



CAUSE
Microsoft is researching this problem and will post new information in the Microsoft Knowledge Base as it becomes available.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
The SQL Server .NET Data Provider uses its own protocol to communicate with SQL Server. It is lightweight and performs well because it is optimized to access SQL Server directly, without adding an OLE DB or Open Database Connectivity (ODBC) layer.

The OLE DB .NET Data Provider communicates to an OLE DB data source through both the OLE DB Service component (which provides connection pooling and transaction services), and the OLE DB Provider for the data source. So the slowness in connection pooling should be negligible when compared to other performance benefits when you use SQL Server .NET Data Provider to connect to SQL Server.

SQL Server .NET Data Provider is recommended for applications that use Microsoft SQL Server 7.0 or later. OLE DB .NET Data Provider is recommended for middle-tier applications that use Microsoft SQL Server 6.5 or earlier, or any OLE DB provider that supports the OLE DB interfaces.

