What Index Attributes Are Supported in the Landmark Database?

Landmark supports the following index functionality not available in Environment 9.0.0:

Index size and expansions
Any field type can be used in an index
Virtual indexes (not backed by physical storage)

Virtual Index Support

A virtual index can be created to aid in database tuning for performance. When a physical index is not required, for example, when an index is used for a report run only infrequently, a virtual index can be created. The database retrieves and sorts the data when requested by the index logic, rather than retrieving a physical set of data already stored in the database.

A virtual index is created as a set definition in LPL. Virtual index use can have both positive and negative performance impacts. A report using a virtual index will take longer to run; however, by removing an infrequently used physical index from the database definition, data stores and updates may be faster in some cases.

A primary or unique index may not be used as a virtual index. The path that is being specified by the virtual index must also be specified in some other physical index in the system.


Index	Fields	Can use as virtual index?
Index 1	A B C	No
Index 2	A B C D	Yes