Re: Most frquently used SQL- Set transaction isolation level

I forgot to mention one other thing....In your original post of this thread you stated "One document from Metalink tells me to look at the section "SQL ordered by Executions" because a small performance increase on a frequently used query can provide greater gains than a moderate performance increase on an infrequently used query." This statement is true. One small SQL statement that gets executed the most often can have performance impacts on your instance. However, one SQL statement that only gets executed five times can cause problems too. This is especially true when you aren't using bind variables. So you might want to look at the problem from the other side of the coin too. That's why Statspack gives you multiple reports on SQL statements and their performance.

HTH,
Brian

Brian Peasland wrote:
>
> I guess the real question is do you need that transaction isolation
> level or not? Can you use the default isolation level? If not, then you
> should probably leave well enough alone.
>
> HTH,
> Brian
>
> "OakRogbak_erPine_at_yahoo.com Kill the 2 trees in email address to reply"
> wrote:
> >
> > Is this a bad thing, like my CPU is doing extra work, or should I just
> > forget about it and look at real SQL statements?
> > -Roger
> >
> > >
> > > This is most likely generated by your ODBC driver for every new connection
> > >
> > > /Erik
>
> --
> ===================================================================
>
> Brian Peasland
> dba_at_remove_spam.peasland.com
>
> Remove the "remove_spam." from the email address to email me.
>
> "I can give it to you cheap, quick, and good. Now pick two out of
> the three"

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"