Posted by Erland Sommarskog on 01/31/06 00:58

kwdavids (kevin@davnet.org) writes:
> For what it's worth...
>
> It turns out that I had set up two "firehose" DataSets on the same
> connection. This resulted in the 2nd connection being opened and closed
> thousands of times by ADO. In my situation, SQL Server is going out to
> lunch after about 6,000 connections.

Or rather shared memory. TCP/IP connections would probably still work
if TCP/IP is enabled, as will existing connection. This was one of the
scenarios I suggested, and I been able to produce this situation myself
when running a tight loop with connection/disconnection without pooling.
(To check for memory leaks.)



--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]