G
George Potemkin
Guest
It's turned out that Progress creates the local indexes using the smarter way! The leading index component has the same value for all records in the same section. It seems that Progress virtually exclude the leading component from the definition of local indexes and the related part of index keys is not stored in the index tree. I wrote: "the compression algorithm works equally well for both key values and RECID parts of the index keys". I was wrong: in this case the local indexes are in fact an equivalent of the the "default" index created by Progress using the "phantom" field when we don't define any indexes for a table. In other words they don't have the index keys and index tree is just a sorted list of recid's. I'm not sure how much space it will safe for an index but definitely an index will use the minimum space.
Continue reading...
Continue reading...