Not only legacy apps, but data warehousing. Frequently in a production
environment you use two sets of tables -- production and data
warehousing...One (production) with "bare bones" indicies to maximize
transaction performance, and one (a replicate in the data warehouse) that
you "index the living
> Legacy apps, Bruce. Sometimes you come across tables with ten fields in the
> index. I'm working on a (fairly specialised) system now where the primary
> key of one of the tables has twenty-four fields in it. It is a summary
> table, and probably not the best design, but that's the way it is,
