Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Problems occur when connecting to SQL Server from ADO application


View products that this article applies to.

This article was previously published under Q300519

↑ Back to the top


Symptoms

When you are using Microsoft Data Access Components (MDAC) version 2.6 from a client application to connect to a SQL Server 7.0 database, the client application may start to experience login timeouts, "Timeout expired" errors, or general network errors. This occurs when the client application is experiencing a high volume of connect and disconnect activity and a large portion of the connections are invalid. Pooling in the Microsoft Data Access Components
http://msdn2.microsoft.com/en-us/library/ms810829.aspx

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
166083� INF: How to enable connection pooling in an OLE DB application
228843� How to implement session pooling from Visual Basic ADO program

↑ Back to the top


Resolution

To work around this problem, Microsoft recommends that you use MDAC OLEDB/ODBC pooling functionality. This will reduce the number of physical connections that are open and connection attempts being made to the database and should prevent the problem from occurring.

This problem also does not occur when you are connecting to a SQL Server 2000 database.

SQL Server 7.0

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301511� How to obtain the latest SQL Server 7.0 service pack

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

SQL Server 7.0
This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.

↑ Back to the top


Keywords: KB300519, kbsqlserv700presp4fix, kbfix, kbbug

↑ Back to the top

Article Info
Article ID : 300519
Revision : 6
Created on : 2/15/2007
Published on : 2/15/2007
Exists online : False
Views : 451