Re: Non-caching of SQL queries

First, thank you for the reply, as it has been a very fruitful discussion (at least for me :-)).

On Dec 1, 6:56 pm, sybra..._at_hccnet.nl wrote:
> You are confusing the buffer cache and the shared pool. Caching sql
> statements will not impact 'the cache available for transaction in
> anwyay'.

Ok, supposed then there is separate preallocated memory for each task, and they will never overlap into one another. So let's take the case of a export file which contains millions of records. So I supposed that when importing all these individual SQL each SQL will go into V $SQLAREA as one record, correct? So:

At some point some of these SQL will be removed from V$SQLAREA correct?
If based on timeout - how long is it? If based on total number of rows in V$SQLAREA, then what is it? Both of these configurable?

> Tom Kyte has written much about the advisibility to cache SQL, if you
> wrote your SQL in such a fashion you use hardcoded literals all over
> the place, you did something fundamentally wrong.
>

Thanks for the reference.

> As far as not caching SQL: just flush the shared pool after every
> statement and notice the performance hog.

This I think could be due to flushing away of all the stored procedures caches which are repetitively used, may be not for the oneoff  SQL. Just guessing.

Sorry if there are any errors....very sleepy now.... Received on Sat Dec 01 2007 - 09:27:47 CST