Clever Geek Handbook

Connection Pool Not Working in .Net SQL Server 2008

I am testing my application hoping to migrate to SQL Server 2008 (200+). In SQL Server Profiler I see

    Audit Login
    SQL: BatchStarting SELECT .....
    SQL: BatchCompleted SELECT .....
    Audit Logout

for every query executed. From what I can tell, this means it creates a new connection for every single request I run, not using a connection pool. This is true? If so, is there anything I can do to fix the problem of why the connection pool won't work. I use one persistent string for connection strings, and I always close (to bring it back to the pool) the connection right after I'm done with it. In my connection string, the pool is disabled and the minimum pool size is 10, the maximum pool size is 1000.

Anyone having similar issues? Just in case this is important, this is an ASP.NET (VB.NET) application running on XP Professional (my development box). I have compiled my web application targeting the .NET 2 framework.

0


source to share


2 answers


This is expected behavior. From the documentation for the Login Audit Event Class :

The Logon Audit event class indicates that the user successfully logged on to Microsoft SQL Server. Events of this class are triggered by new connections or connections that are reused from the connection pool.



You should look at the respective connection performance counters to see how many connections you actually have (client and server).

+4


source


To answer your question, No. This behavior does not mean that your connections are not merging. As casper explained, you will see these events even when the pooled connections are reused.



0


source






More articles:


All Articles