5.4SP2 Through prconfig.xml
file settings, you
can identify database operations that return thousands of rows. Such
operations can impact performance, even when the total number of bytes
(for all rows combined) is small. In an alert log, the following message
appears.
PEGA0027 *NA*Database list returned more rows than threshold allows
Other fields in the alert log message identify the pzInsKey value of the current activity.
This facility is enabled by default, with a threshold of 25,000 rows. To establish another threshold:
1. Update the alerts section of the prconfig.xml
file,
setting a larger or smaller desired threshold in bytes:
<env
name="alerts/database/rowReadThreshold/enabled"
value="zzzzz" />
<env name="alerts/database/rowReadThreshold"
value="nnnnn" />
where nnnnn is a positive integer identifying the number of rows in the query result.
Set the enabled
value to false
to disable
this alert. The default is true
.
2. Stop and restart the server.
This alert focuses on the number of rows returned. Other alerts bring attention to the elapsed time for a database operation or the number of bytes returned. Each alert can identify specific items for performance analysis and improvements.
alert log, prconfig.xml file | |
Understanding
alerts
Working with the PegaRULES database |