Hi,
I got a question from a partner.
According to them, they upgrade Pega production environment from v7.x to v8.7 with the database schema being single.
The question I received is whether it is a mandatory requirement to split the schema to data and rules just before upgrading from v8.7 to Infinity’23 or not.
We know that the advantage to split the schema and recommended them to do that. But they just want to confirm the possibility to upgrade with single schema just in case.
It would be a great help if someone could tell us.
Thank you in advance,
Nobuyuki Tateno
@Nobuyuki Tateno While it is highly recommended to use a split-schema configuration for the benefits it provides, such as minimal to zero downtime during upgrades, it is not a mandatory requirement for upgrading from Pega 8.7 to Infinity '23. However, please note that using a single schema may increase the amount of time your system must be unavailable during an upgrade.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
Understanding a split database architecture > Split schema database architecture
Planning a Pega Platform installation > Understanding Pega Platform split-schema
Patching systems without downtime (for Pega Platform version 8.4 and later)
Performing your update
Please can you find the relevant PO internally to ask your question if you need further help?