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

Performance issues with queries on unexposed properties



Users are observing long wait times (20+ seconds) when running reports or accessing functionality that reports on unexposed properties. Many PEGA0005 alerts are found in the PegaRULES-ALERT logfile.

Error Messages

PEGA0005 alerts similar to the following:

Database operation took more than the threshold of 500 ms: 2,772 ms SQL: SELECT DISTINCT PEGADATA.pr_read_from_stream('.pyFlowName', "PC0".pzInsKey, "PC0".pzPVStream) AS "pyFlowName" , PEGADATA.pr_read_from_stream('.pyAssignmentClass', "PC0".pzInsKey, "PC0".pzPVStream) ...WHERE ( "PC0".PXHISTORYFORREFERENCE = ? AND PEGADATA.pr_read_from_stream('.pyAssignmentClass', "PC0".pzInsKey, "PC0".pzPVStream)

Steps to Reproduce

Not Applicable

Root Cause

PEGA0005 alerts that document queries that use pr_read_from_stream() indicates that the properties included in the query are not optimized for reporting. This is particularly critical for criteria (WHERE) clauses.


Optimize the properties for reporting.

Furthermore, properties used in WHERE clauses should typically have indexes built on them.

Published August 26, 2017 - Updated 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