How can one optimize tables, if the process redefines the primary keys?
One table has a field that refers to the primary key of the other table.
If the keys are redefined, the table will be wrong.

Sanford Aranoff wrote:
> How can one optimize tables, if the process redefines the primary
> keys? One table has a field that refers to the primary key of the
> other table. If the keys are redefined, the table will be wrong.

It does not redefine the primary keys or change any other data. It optimize
a table using the primary index as the main factor.

Ralf

Sanford,

<< How can one optimize tables, if the process redefines the primary keys?
One table has a field that refers to the primary key of the other table. If
the keys are redefined, the table will be wrong. >>

It doesn't change any primary key values, it simply re-orders the physical
records according to the chosen index.  This optimizes the read-ahead on the
table using the most-often-used index (hopefully that is the index that you
chose during the optimize), which can result in pretty good performance
gains.

--
Tim Young
Elevate Software
www.elevatesoft.com