The Pega Platform database and the tables within it are structured in a unique way. By understanding how the database is structured, you are better able to support system upgrades and to be responsive to changes in data utilization.
To use other databases in your Pega application to accomplish your workflows, see Creating database data instances
Connection pool settings for your Pega Platform database
Pega Infinity is an application requiring a high database connection request and return rate. In Pega Cloud services environments, Pega manages the connection pool settings across the fleet of systems that are appropriate for the range of client’s business needs, based on our experience. Clients cannot change or request changes to the default configuration.
For clients not using Pega Cloud services environments, to ensure that your data is persisted throughout any period of intensive database processing, Pega recommends using the following connection pool settings (on a per node basis) during the Pega Platform installation process, as described in the Installation and Update Guides:
Connection pool default settings
|Per node setting||Recommendation|
|Initial Pool Size||0|
|Minimum Pool Size||3|
|Maximum idle connection count||25|
|Maximum Pool Size||75|
|Connection Validation Strategy||Test upon requesting any connection.|
|Connection Validation Method|
Use the JDBC4 driver’s default validation method (isValid() API) instead of a providing a specific validation SQL.
Pega recommends this approach to minimize connection pool changes as database vendors provide updates to either their products or drivers. It also ensures that the pool is configured to use the vendor’s best practice for validating the connection.
|Idle Connection Eviction Policy||Enabled|
|Eviction Thread Run Frequency||5 seconds|
|Idle Connection Timeout||1 minute|
|Socket Timeout||90 seconds|
|Connection Creation Wait Timeout||10 seconds|
These settings will allow most clients’ database connections to maintain stability and scale up or down in line with the end users and processes that are running on most client systems. Pega recommends starting with a relatively high maximum pool per node, to be able to handle high usage, a low idle timeout per node for prompt eviction, a low minimum pool per node to avoid database connection overhead during quite periods, and a reliable connection validation.
If a non-Pega Cloud services client's organization or specific database vendor software version recommends settings that conflict with these recommendations, a database administrator from your organization should reach out to your Pega representative to manage these settings before you install Pega software.
- Configuring a split database architecture
Pega Platform high availability is database-agnostic. The recommended database features are:
- Viewing database tables and Pega Platform metadata by using the Clipboard tool
Every persistent object in the Pega Platform database has an associated class ( Rule-Obj-Class rule type). The Pega Platform uses a simple algorithm and information in Data-Admin-DB-Table instances to determine which table contains objects of which classes.
- Database naming conventions
When the Pega Platform database is initially installed, object names follow specific naming conventions. Tables and view that you add do not have to follow these conventions.
- Database views
- Understanding the default database tables
The Pega Platform contains database table ( Data-Admin-DB-Table ) data instances when it is initially installed. These instances are linked to various database tables and views in the Pega database, and are used to map classes or class groups to database tables or views.