Re: How to avoid soft parses with ADO
- From: "sjaffarhussain@xxxxxxxxx" <sjaffarhussain@xxxxxxxxx>
- Date: 6 Jun 2006 00:54:33 -0700
Did you set session_ casched_cursor?
It seems to be library cache contention.
Do you also use synonyms?
If possible, read, Metalink Note : 1012049.6Tuning Library Cache Latch
Contention
Tzanko wrote:
Hi,
We have an application using Oracle DB through ADO - Oracle OLEDB
Provider for Oracle. I am monitoring the performance of the applciation
with heavy load, and I can see that our hard parse ratio is good (2% of
queries are being hard-passed) (and we are using bind variables in
queries that are execured most often), but too many SQL queries are
soft-parsed - say 80, 90%. We are using ADO and we create the ADO
connection object and recordset object as required and then release as
soon as we've finished with them, following ADO recomendations. We
believe the connection is pooled and therefore it is better to release
as soon as possible rather than hold it for a duration of a transaction
or between transactions.
In this scenario, can anyone suggest what can be done to reduce the
number of soft parses. Oracle recomend that 30% of soft-parses as a
treshold. The rest 70% of the queries should not require parsing at
all.
Thanks
Tzanko
.
- Follow-Ups:
- Re: How to avoid soft parses with ADO
- From: Tzanko
- Re: How to avoid soft parses with ADO
- References:
- How to avoid soft parses with ADO
- From: Tzanko
- How to avoid soft parses with ADO
- Prev by Date: Re: SQL 2005 Reporting Services querying an Oracle DB
- Next by Date: Re: Using Date Mask on ET Make No Rows Returned
- Previous by thread: How to avoid soft parses with ADO
- Next by thread: Re: How to avoid soft parses with ADO
- Index(es):
Relevant Pages
|
