Replicated and split databases

In general, the Pega Platform data can be replicated or split to support high-volume production requirements, reporting, or other needs.

Database vendor facilities that implement replication do not affect the Pega Platform operation. Separate server nodes can access tables in separate, but synchronized, database instances.

CAUTION:
Never replicate the pr_sys_updatescache or pr_sys_locks tables. All nodes in a multinode Pega Platform system must access a single copy of these two tables.

In addition, in a production system the rules change slowly and frequently used rules are cached. Work items, work item history, and work item attachments can grow to require more space than rules.

See the PDN article Benefits of placing rules in a separate database from transaction data for a discussion of the advantages and disadvantages of splitting the database.