Reduce row chaining - when/how ?

Hi,

I was wondering when a DBA should do something about row chaining :

one of my three biggestr tables jas 5% chained rows.

At wich treshold should I act.

To reduce it I see 3possiblities :

1. * lock table for update
   • copy all data to a tempory table
   • delete all data
   • insert from temp-table
   • commit;

  ? will the lock stay ones all data is deleted ??

2) export / import --> not possible since the database haa tow remain up , the table has to stay actif.

3) same as 1 but only for the chained rows

Does anyone automates his search for chained rows, + an automated solution to 'unchain' ?? Received on Thu Aug 08 1996 - 00:00:00 CEST