In some cases, running reports — by either agent processing or application users — can impact performance because of high demands on database processing. To reduce the performance impact of running reports, you can specify that some reports obtain data from a separate reports database, which is a copy of all or part of the PegaRULES database.
The reports database must have the same structure (tables and columns ) of the PegaRULES database. A reports database might contain only a subset of the tables needed for reporting, and might contain old data.
To set up a reports database:
To disable use of a reports database, even when the Use alternate database option is selected, add the following entry to your prconfig.xml file.
<env name = "database/useReportingDatabase" value="false" />
The default value is true.
As an alternative to modifying 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 substantial.
For list view and summary view reports, to force the use of a reports database for standard reports (for which the Use alternate database? option is not selected), set the pyUseAlternateDb
parameter to true when calling the Rule-Obj-ListView.ShowView or Rule-Obj-SummaryView.ShowView activities.
About Database Table data instances | |
Atlas — Standard Database Table instances |