Hi
Is anybody using connection pooling?
The standard method what I saw is following - on every page: open new
connection, make select, close connection. So, if one user visit one by one
10 pages - 10 connections will be created and destroyed. Some bad way, isn't
it?
A
"RunneR"
news:418d5352_1@news.estpak.ee...
> Hi
>
> Is anybody using connection pooling?
Yes.
> The standard method what I saw is following - on every page: open new
> connection, make select, close connection. So, if one user visit one by
one
> 10 pages - 10 connections will be created and destroyed. Some bad way,
isn't
> it?
No.
Bob Lehmann
RunneR wrote:
> Hi
>
> Is anybody using connection pooling?
> The standard method what I saw is following - on every page: open new
> connection, make select, close connection. So, if one user visit one
> by one 10 pages - 10 connections will be created and destroyed. Some
> bad way, isn't it?
>
> A
No, 10 connection will NOT be created and destroyed, unless they are created
more than 60 seconds apart. Connection pooling (actually called "session
pooling" in OLEDB) is the default behavior. When a connection is closed and
destroyed on the page, it is actually moved into te pool of connections so
that the next time a connection is requested, the one from the pool is used.
http://support.microsoft.com/?scid=kb;en-us;Q176056
http://support.microsoft.com/default.aspx?scid=kb;en-us;1915 72
Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
> Is anybody using connection pooling?
Most of us are, yes.
> The standard method what I saw is following - on every page: open new
> connection, make select, close connection. So, if one user visit one by
one
> 10 pages - 10 connections will be created and destroyed. Some bad way,
isn't
> it?
No, you misunderstand how connection pooling works.