Connection String Property For Pooling

  • Thread starter Thread starter dmac
  • Start date Start date
D

dmac

Hi.
Just a quick quastion. There seems to be a close relationship
between connection pools and the connection string. Given that a
Workstaion ID forms part of a connection string, does this mean that
each machine on the network that will access the server will always
start and use its own pool,a thus a very small pool size is approriate
to allow as many of these 'user' pools as possible?

Dave
 
Hi,

Connection pool lives on a client, yes.
I guess this explains everything :-)
 
¤ Hi.
¤ Just a quick quastion. There seems to be a close relationship
¤ between connection pools and the connection string. Given that a
¤ Workstaion ID forms part of a connection string, does this mean that
¤ each machine on the network that will access the server will always
¤ start and use its own pool,a thus a very small pool size is approriate
¤ to allow as many of these 'user' pools as possible?

Depends upon where the connection is established. If it's established on the client then yes the
connection pool is local and specific to the application process in which it was created. If it's
established via a web server, or other remote process host such as COM+, then the pool is created
(and typically shared) at the application process level on the remote resource.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top