Re: MinPoolSize behaviour

From: Angel Saenz-Badillos[MS] (angelsa_at_online.microsoft.com)
Date: 03/18/04 

Date: Thu, 18 Mar 2004 02:15:44 -0800

Too many issues, lets take them one at a time:

Performance monitor: this accumulates, there is a kb available on this
somewhere and it is not our fault, unfortunately this makes this feature
very unreliable.

Min Pool Size, The first time you open a connection we will open the 1
connection and return, on a background thread we will start to open
connections on the server until Min pool size is reached, Min Pool Size is
guaranteed from that point on.

Is the pool created forever? the "pool" is created per Process per
Appdomain, if the process or appdomain where the pool resides goes away so
does the pool. There is an extremely good article on how pooling works here:
http://www.sys-con.com/dotnet/article.cfm?id=483 I highly recommend reading
this article by Guy Smith-Ferrier.

Hope this helps 

-- 
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
"Stefan Turalski (stic)" <stefan.turalski@kruk-inkaso.com.pl> wrote in
message news:uYvC33qCEHA.3064@tk2msftngp13.phx.gbl...
> Hi,
> I've read this paper on M$ sites, and first answer to Roberts question is
> yes - there are objects created in advance,
> but there is another question for which answer I also looked up some time
> ago..
> Is the pool created forever ?
> That's means, if I create sqlConnection which one connection string. Then
> use open(), close() and even kill the application this pool still will be
> there ?
> Time needed to make open connection at first time when I run my test
> application is around 289ms, when I close connection and open it (before
> restarting app.) it is around 0ms. Now when I restarted then I agein
obtain
> ca. 300ms - that's seems like this pool is dead.
>
> But at Performence Monitor -> .NET CLR Data, counter Current # connection
> pools - still is growing, no (as I asume) still be around 0 - if there is
no
> running app. or 1 if I run one (or x if I run X more)...
>
> So where I'm wrong ? Pools are immortal, or sth like this  ? ;-)
>
> --
> best regards
> stic
>
>
> Użytkownik "Teemu Keiski" <joteke@aspalliance.com> napisał w wiadomości
> news:uX%23mSt6BEHA.712@tk2msftngp13.phx.gbl...
> > Hi,
> >
> > when the connection pool is created (one pool exists per unique
connection
> > string used), the minimum count of connection objects, given in Min Pool
> > Size,  are created and added to the pool.
> >
> > More information about the connection pooling:
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconnectionpoolingforsqlservernetdataprovider.asp
> >
> > -- 
> > Teemu Keiski
> > MCP, Microsoft MVP (ASP.NET), AspInsiders member
> > ASP.NET Forum Moderator, AspAlliance Columnist
> >
> > "Robert Scheer" <rbscheer@my-deja.com> wrote in message
> > news:cfd22ab6.0403111115.15e8a964@posting.google.com...
> > Hi.
> >
> > I think I have basic questions here, but maybe I'm on the right group.
> >
> > Suppose I set the MinPoolSize of a connection to 10. Then I open and
> > close the connection for the first time in my application. When I
> > close the connection, will ado.net creates 10 connections in advance?
> >
> > Since the MinPoolSize says 10, does it mean that I will have 10
> > connections in my pool forever?
> >
> > Thanks,
> > Robert Scheer
> >
> >
>
>

Relevant Pages

  • Re: Close and Dispose argument
    ... > fact that even Microsoft is not clear on the issue. ... > connections from the pool is still a debate. ... > method removes the conneciton from the connection pool". ... > Your issue was forwarded to us here at Microsoft Courseware Support. ...
    (microsoft.public.dotnet.framework.adonet)
  • Close and Dispose argument
    ... here is an email conversation between me and Microsoft ... connections from the pool is still a debate. ... Programming with Microsoft ADO.NET" module 2, p 18: "Calling the Dispose ... method removes the conneciton from the connection pool". ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Q:Multithreaded ADO.Net Connections Are Non Pooled?
    ... different you get a new pool. ... > the process/app domain differences, does running on a thread created by ... If you're using SSPI, each connection must be ... >> connect to the SQL Server machine, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Connection pooling and changed password issue
    ... There is no "clear the pool" or "drop the pool" until ADO.NET 2.0. ... > Hi - so a previously made connection with the old credentials will still ... > "William Vaughn" wrote: ... >>> username/password then the connection pool will be used and the same ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MinPoolSize behaviour
    ... I've read this paper on M$ sites, and first answer to Roberts question is ... Is the pool created forever? ... if I create sqlConnection which one connection string. ... Time needed to make open connection at first time when I run my test ...
    (microsoft.public.dotnet.framework.adonet)