Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SQL query performance degrades due to missing database INDEX

SA-54520

Summary



A Process Commander Autonomic Event Server (AES) instance reports poor performance on a standard Process Commander SQL Statement.

Below is the poorly performing SQL statement:


SELECT
  pzInsKey as "pzInsKey" ,
  pyRuleSetVersionID as "pyRuleSetVersionID" ,
  pyRuleSetName as "pyRuleSetName" ,
  pxObjClass as "pxObjClass" ,
  pyVersionSecure as "pyVersionSecure" ,
  pyLabel as "pyLabel"
FROM
  RULES.pr4_rule_ruleset
WHERE
  pyRuleSet = ? and
  pxObjClass = ?
ORDER BY
  pzInsKey



Error Messages



Not Applicable


Steps to Reproduce



Unknown


Root Cause



The database INDEX was missing.


Resolution



Perform the following local-change:

Provide the below database INDEX.


CREATE INDEX
  RULES.PR4_RULE_RULESET_IDX3
ON
  RULES.PR4_RULE_RULESET
(
  PXOBJCLASS      ASC,
  PYRULESET       ASC,
  PZINSKEY        ASC
);

Published October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us