Tools like PLSQL Developer allow you to analyze your SP quite easily.
--
Terry Dykstra
Canadian Forest Oil Ltd.
"PierIgno" <PierIgno_at_pippero.it> wrote in message
news:dkdg8g$pno$1_at_stargate1.inet.it...
> Jonathan Lewis wrote:
> > "GeoPappas" <PappasG_at_gmail.com> wrote in message
> > news:1131031547.194467.279820_at_f14g2000cwb.googlegroups.com...
> >
> >>I am familiar with the ability to tune a SQL statement, but is there a
> >>way to tune a procedure?
> >>
> >>For example, we have a procedure in PL/SQL that is a few hundred lines.
> >>I would like to test the procedure and capture a benchmark. I would
> >>then like to try various things to try and improve performance.
> >>
> >>Is utlbstat/utlestat the best way?
> >>
> >>Are there other ways?
> I usually put a session under trace and I use tkprof....
> >>
> >>FYI: Using Oracle 10g on Solaris 2.9
> >>
> >
> >
> >
> > Take a look at the dbms_profiler package.
> >
> > This allows you to capture the number of visits
> > to, and time spent in, each line of the pl/sql. So
> > it tells you which bits of code need tuning, and
> > lets you know if you've got any code paths that
> > haven't been tested by your data.
> >
> > The overhead while running a test is, obviously,
> > rather large.
> >
> >
Received on Thu Nov 03 2005 - 13:24:17 CST
