Setting up a reports database

In some cases, running reports 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.

1. Work with a database administrator to create the reports database, identifying the tables, indexes, and views to include.
2. Work with a database administrator to set up database replication, which uses a mirroring technique.
3. Create a database data instance (Data-Admin-DB-Name) for the reports database and establish connectivity.
4. Update the Database Table data instances to identify this database in the Reports Database field.
5. Select the Use alternate database check box on the Data Access tab of report definition rules that are to extract data from the 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" />

Note: The default value is true.

Use of a reports database is less helpful in situations where JVM memory, CPU processing, or network traffic are substantial.

To force the use of a reports database for standard list view and summary view reports when 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.

Related information

Open topic with navigation