-----BEGIN PGP SIGNED MESSAGE-----

The system index automatically defined on a foreign key column cannot
be set inactive then active in order to rebuild it. It can't be
dropped and recreated too.

So after a mass insertion in a table with foreign keys, a set
statistics is all what can be done to the indexes to get them back in
better shape.

Here is the design question : why are the indexes on foreign keys
made mandatory ? Wouldn't it be acceptable to make them 'dropable' or
at least allow them to be set inactive (then active again) ?

Only the cascading of an update or delete on a primary key would
suffer (possibly heavily) of the temporary absence or inactivation of
the foreign keys indexes. At least they could be rebuilt without
backup-restore. But after all, is there any value in willing to
rebuild the foreign keys indexes ?

Olivier Mascia, om@...
T.I.P. Group S.A., www.tipgroup.com




-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8

iQEVAwUBOgElQqIodNUVZIMJAQFsOgf/VAFeUGozG24c3UiO8I3GDjmM/BYss9M9
n3QVYMDaU8bI4DneDyYSW1bzn4bmYOM4JeQKu65TFE9AGl93AKhNyOkur4esAtNP
faRDsPYPIhNVYEp5tTD0WwZutisGLujdfWUTn9FYRjDdH56cSv9QzDgYsJIYLSx1
jGMjZz/1FsA18efc9kuue8lA2GRexKK5bWly4uE6pNDrIFU/rr2XjTaF+w2L5Ns+
zcLQrgzCRqU/PGEq4E1phg8s0C3oYh034X6XrYckNd8LBEIClkUNj0KvtrSQOAcT
Ihgd9Kgektp65V+zy6y+dEWvfzQtHAdSBo41ZQ61KMeGvkrOwumJ1w==
=bl4J
-----END PGP SIGNATURE-----