I'm working on a database in which I need to add a column to a high-volume transactional table. I'd like to have this column protected by a FOREIGN KEY constraint but the column will probably never need to have a complete index on it -- in fact, it's critical to not add any more indexes to this table. R:Base provides the SET FASTFK ON option for this situation. Unfortunately, it operates on the entire database so once I set it on and reload the database all my foreign keys will be converted to the "fast" version. I can write a little program to read the SYS_INDEXES table and write a script with a lot of CREATE INDEX commands to put back the full indexes on those FOREIGN KEYs in the system that also require a full index (this is what the documentation suggests). At the same time, I may find some other FOREIGN KEYs for which I don't need full indexes, thus improving the performance of the database. This seems like a major change, fraught with the possibility of getting something wrong during the transition. Does anyone have experience running their database with FAST FK set to ON? --Larry
