• It's a products table... it has VAT, warranty, supplier, units, .... and many other references.

    The referenced tables don't have many records (top on has 20) but the products can have 16000 or many many more...

    And since the referenced tables can't be updated (code column is read only after insert) it can only be deleted what doesn't happen that much...

    Referenced tables with few records usually means that it isn't inserted/updated/deleted that regularly (in our case the tables are configured usually once and left alone) so narrow indexes on the primary table for these ones can be a rule to break... I guest..

    We also have some other cases that probably require the primary table index...

    In cases were the FK columns can't be updated cause they are read-only and the data isn't deleted (just a bit column with record state) the indexes don't make sense right?

    Thanks,

    Pedro



    If you need to work better, try working less...