ADO - Bad when it is time to Optimize
- From: cvsudheer@xxxxxxxxx
- Date: 8 Mar 2007 19:37:56 -0800
I am working on a huge application where the business components are
in COM-ATL and the data access is thru ADO to SQL.
We are having major scalability issues with huge user connections and
then it was time to see whether are we using the ADO pooling in the
right way. But to my surprise I noted that there is no way to monitor
the ADO pool and its performance.
1. You cannot set the max pool size.
2. There is no way to disable the pooling
3. You cannot know whether non-pooled connections are happening
4. Donot know whether connection creeping is happening.
5. There are no performance counters to get some data abt pools. But
there exists counters for ODBC which microsoft does not support.
The only way to check whether pooling is happening is thru the SQL
Profiler where for every connection reused from the pool, you can see
SP_RESET_CONNECTION stored procedure being called.
Yes ..You can check the pools, the connections, thier life time by
taking a hang dump, provided you have ADO private symbols..!
This is with classic ADO.
Dont ask me to use ADO.NET (I already have some.). There there is no
way control the time a connection lives in the pool. But there is one
in ADO (SPTimeout).
It is really pathethic to find that when you find that there is no way
to get an idea about the health of the ADO Pooling.
If anybody knows about any tool, code etc. please do let me know.
Thanks!
SK
.
- Follow-Ups:
- Re: ADO - Bad when it is time to Optimize
- From: Bob Barrows [MVP]
- Re: ADO - Bad when it is time to Optimize
- Prev by Date: Re: Incorrect Syntax Near (table name). why ??
- Next by Date: Re: ADO - Bad when it is time to Optimize
- Previous by thread: Re: Incorrect Syntax Near (table name). why ??
- Next by thread: Re: ADO - Bad when it is time to Optimize
- Index(es):
Relevant Pages
|
|