Re: Truncate table, rebuild index?

On 3 Set, 22:56, "Jonathan Lewis" <jonat..._at_jlcomp.demon.co.uk> wrote:
> "Andrea" <netsecur..._at_tiscali.it> wrote in message
>
> news:1188816830.056581.215740_at_k79g2000hse.googlegroups.com...
>
> > hi,
> > for some management works i've truncate a table with reuse storage
> > option and next i run "insert" for repopulating table with the same
> > original data. In this case, is useful to rebuild indexes of the table
> > or not?
>
> > thanks for your response
>
> > bye
>
> Where does the data come from that you insert to "repopulate"
> the table. Is the whole exercised aimed at copying out a small
> fraction of the table to get rid of most of the data, then copying
> it back in ? If so, then "insert /*+ append */" would be your best
> option as this will insert the data without generating UNDO for
> the table, and will do a delayed index build (rather than row by
> row maintenance) that will be at least as effective as a separate
> "create index" in terms of resource usage and index packing.
>

thanks very much Jonathan for the advise is exactly what i want to make, reinstert clean data in the table. The rows in the original table are 544000 (avg of 80 byte for each entry)
but if i get rid of most of the data they become less then 500000. The indexes are all normal B*tree on 9i DB.

i was just reading your paper "When Should You Rebuild an Index?" from dbazine.com.
it has been a pleasure to know to you :) Received on Tue Sep 04 2007 - 03:24:44 CDT