Re: Connection Pool in SQLserver 2005
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Fri, 3 Nov 2006 09:00:49 -0800
If the users are constantly in/out of the server, you can still benefit from
using connection pooling. It's just that each user will have their own
connection pool. (Set the max connections in the pool to 2, and set the pool
timeout up to 10-20 minutes -or longer.)
Of course, this will require a bit more memory on the IIS box, and a bit
more on the SQL Server, but will greatly improve responsiveness.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"jcjj" <jcjj@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CD85E9F3-21BE-42B6-AC23-EDBF0234C713@xxxxxxxxxxxxxxxx
What is the performance cost of not using connection pool when connecting
to
a sqlserver 2005 using windows identity.
We are planning an application where the users windows identity is
forwarded
through all layers all the way into the sqlserver.
This gives security and auditing advantages.
But a pros/cons evaluation is always proper to do.
The cons include: the sqlserver connection pool cannot be used...(?) If
there is more problems, pls let me know.
This rises the question: what is the price for not using connection pools.
Who is paying: the sqlserver or the business layer on the IIS server or
both?
regards
Jens Chr
.
- Prev by Date: Re: Cannot connect to SQL Express on 2003 Machine from XP machine
- Next by Date: Re: Cannot connect to SQL Express on 2003 Machine from XP machine
- Previous by thread: Obtain Mcse,Mcsa,Mcdba,Mcsd .Net,Ccna,Ccnp Without Exams(Pay After Check Resutls)100% Passing Gaurantee
- Next by thread: Connect via workgroup
- Index(es):
Relevant Pages
|
