Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Database indexes

Updated on May 11, 2022

When initially installed, the Pega Platform contains indexes that provide fast alternate access to rule information through the use of alternate (secondary) keys. These indexes have low or zero turnover (additions and deletions) in a production system. Other indexes support system operations such as locking and usage tracking, and can have high turnover.

For example, the database index flow_pyClassName associates flow names to Work- classes, and changes only when flows are added or deleted.

Note: Database indexes are not the same as instances of concrete classes derived from the Index- base class. Their purpose and function are similar; however, database indexes are supported by database software.

Index- objects, created by Declare Index rules ( Rule-Declare-Index rule type), support application-specific access.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us