Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Connection pooling problem w local client on Win2003

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2005-12-16 : 08:07:09
Jaroslav writes "For performance reasons we have (successfully) used pooling in our apps and services on almost one hundred installations, NT 4.0 to 2000 servers (SQL 7.0 - 8.0), NT 4.0 to XP workstations without a problem in any combination.

Now with 5.2 (2003) server a local client is unable to connect and crashes within the SQLDriverConnect call (SQLConnect as well). Does not return at all.

When the same runs on any other client (4.0, 2000, XP), everything is OK.

The problem comes and goes with SQL_ATTR_CONNECTION_POOLING

100% sure the bug is not in our code - the pure MS-supplied code as shown in Q164221 crashes precisely the same way.

When SQLSetEnvAttr(...SQL_ATTR_CONNECTION_POOLING...) is not used, it's ok,
BUT:
To quit using benefits of pooling is a solution with severe impact on performance.

Any hint?

TIA

Jaroslav Pivonka

// Windows Server 2003, 2 in a cluster
// SQL Server 2000 EE SP4 (8.00.2039)"
   

- Advertisement -