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 updates 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
Pega Platform is an application requiring a high database connection request and return rate. In Pega Cloud 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. Pega Cloud clients cannot change or request changes to the default configuration.
- Custom connection properties required for disaster recovery
To maintain the stability of your Pega application in the case of a network or database outage, your application must have an appropriate recovery time to clean up broken connection sockets caused by the outage.
- Database tables and views
You can make changes to database tables to support your Pega Platform needs. Because Data-Admin-DB-Table and Data-Admin-DB-Name instances control how the Pega Platform finds objects within the Pega Platform database, changes to the database table structure must be coordinated with changes to these data instances.
- 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.
- Split database architecture
Pega Platform high availability is database-agnostic. The recommended database features are:
- Java user-defined functions in your Pega database
Beginning in Pega Platform version 8.6, Pega deprecated usage of the Java user-defined functions (UDFs) due to their severe performance impact. In a future release of Pega Platform, Pega will no longer support Java UDFs for on-premises deployments.