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