Execution of V5 reports — summary view rules and list view rules — by application users or by agent processing may provide a substantial source of database processing database demand in some cases.
To reduce the performance impact of V5 report execution, you can direct that some reports obtain data from a separate reports database, which is a copy (a replicated mirror) of all or part of the live PegaRULES database.
The reports database must have the same structure (tables and columns ) of the live database, but may contain only a subset of the tables needed for reporting, and may contain slightly stale data.
To use a reports database:
To disable use of a reports database even when the Use alternate database? option is set and the Reports Database field is not blank, add the following entry to your prconfig.xml file.
<env name = "database/useReportingDatabase" value="false" />
The default value is true.
As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.
See How to create or update a prconfig setting.
Use of a reports database is less helpful in situations where JVM memory, CPU processing, or network traffic are more
To force the use of a reports database even for standard reports (for which the Use alternate database? option is not checked), set the pyUseAlternateDb
parameter to true when calling the Rule-Obj-ListView.ShowView or Rule-Obj-SummaryView.ShowView activities.
Reports based on report definitions do not support the reports database feature; such reports always use data from the live PegaRULES database.
reports database | |
About Database Table data instances
List View form — Completing the Content tab Summary View form — Completing the Content tab |
|
Atlas — Standard Database Table instances |