Title: Re: Shrink Table: IEstimating Rollback Space
|
Insert operations are *ALWAYS* faster (i.e. using direct-path) and more
scalable (i.e. using parallel) than update/delete operations;
direct-path operations pretty much eliminate undo, and NOLOGGING option
for direct-path can pretty much eliminate redo. Rebuild is essentially
an insert operation, same as move. So, move/rebuild will absolutely
take less elapsed time than shrink (unless the environment is short of
CPU/IO resources); the only thing in favor of ALTER TABLE ... SHRINK
SPACE is the online capability. It's the age-old "speed vs flexibility" trade-off that permeates just about everything in computing. It's nice to have a choice. Ian MacGregor wrote: Move requires rebuilding of the indexes. I’m nrt sure it will be quicker.-- //www.freelists.org/webpage/oracle-l |