Re: Table extents

Both options would work, as long as you take care to ensure that grants and constraints are preserved. However, I don't class these objects as having a large number of extents and why is this a problem anyway? If the tables had a high percentage of chaining then I would go to the trouble of rebuilding, otherwise I probably wouldn't bother.

> I recently took over support for an app that has very
> little back end
> documentation. An automated message was generated saying
> I had 3 tables
> with "Extreme Fragmentation". Looking closer I saw that
> the following
> tables has the following extents:
> table1_ancientapp 89 extents
> table14_ancientapp 9 extents
> table22_ancientapp 8 extents
>
> In looking to rectify the situation, I was thinking of
> performing the
> following procedure
>
> drop indexes on table1_ancientapp, export
> table1_ancientapp, drop
> table1_ancientapp, create table1_ancientapp, import the
> data back in,
> rebuild the indexes.
>
> I understand that I can also create a new table by doing a
> select from the
> previous one, drop the previous table and rename the new
> table to the old
> ones name, but would this have the same result as the
> above?
>
> Is either of these the solution I want to use to remedy
> the situation?
>
> Thanks
>
>
Received on Mon Sep 10 2001 - 14:46:13 CEST