Re: hard vs soft parse

Thanks! But how to avoid soft parsing?

Oracle Magazine Sept/Oct publishes an article on Statspack: "A high soft parse rate is important because unnecessary soft parses limit application scalability. Ideally, a SQL statement should be softparsed  once and per session and executed many times."

Should the application keep a cursor on each SQL statement to avoid soft parsing?

/Armin

In article <8vde8d$2ug$1_at_nnrp1.deja.com>,   sybrandb_at_my-deja.com wrote:
> In article <8vd90r$u9t$1_at_nnrp1.deja.com>,
> arminseidel_at_my-deja.com wrote:
> > Oracle tuning books distinguish between hard and soft parsing of SQL
> > statements. However, I haven't found any description of the
 difference
> > between hard and soft parsing.
> > Can you explain the two types of parsing?
> > Tuning measures?
> >
> > Thanks,
> > Armin
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
> >
> If a statement is submitted and it appears to be already in memory
> (whether the same or a different user) this is considered a soft
 parse.
> If it is not in memory it needs to be parsed completely: this is a
 hard
> parse.
> Tuning measures: never use hardcoded literals, always use bind
> variables and always write your statements exactly the same.
>
> Hth,
>
> --
> Sybrand Bakker, Oracle DBA
>
> All standard disclaimers apply
> ----------------------------------------------------------------------
 --
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue Nov 21 2000 - 07:36:00 CST