Skip to main content

Table of Contents

Understanding the unique features of the Pega Platform database


Only available versions of this content are shown in the dropdown

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 Guide:

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 jdbc4 default API isValid()
Idle Connection Eviction Policy Enabled
Eviction Thread Run Frequency 5 seconds
Idle Connection Timeout 1 minute
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.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us