Kenneth is right. Set up a cron job to analyze your tables on, say, every
Sunday night. The DBMS_JOBS package makes it easy to do.
Kenneth C Stahl <BluesSax_at_Unforgettable.com> wrote in message
news:37B31910.E9B22D56_at_Unforgettable.com...
> I don't think there is any real rule for this, but in general if a table
has
> less than 1000 rows you probably won't see much difference if it is
analyzed or
> not. On the other hand, tables with over 1000 rows can benefit greatly by
being
> analyzed.
>
> On the system I work with I have a cron job that analyzes all of the
tables
> during a non-peak period.
>
> Ken
>
> Duncan Hodson wrote:
>
> > Hi all,
> >
> > Our application inserts a large number of records into several large
tables.
> > After a while performance degrades and we find that performing an
analyse
> > table on these tables improves performance dramatically.
> >
> > Is there any way to get Oracle to tell me which tables need analysis
before
> > performance starts to degrade? Can i find this information from the
oracle
> > data dictionary?
> >
> > Cheers in advance
> >
> > Duncan Hodson
>
Received on Thu Aug 12 1999 - 18:00:05 CDT
