Interaction History Database Tables in a Dedicated Schema in Pega 7.2.2
Hi,
Is it still recommended/relevant to install Interaction History Database Tables in a Dedicated Schema?
What are the pros and cons of doing it?
I can see this mention in the Decision Strategy Manager 7.2.2 Upgrade Guide but nothing in the Pega 7 Platform installation guide (v7.2.2 Tomcat-Oracle).
We are doing a new Pega 7.2.2 + Pega Marketing 7.22 install so would appreciate the ideal and optimum (for Production) setup recommendations.
Thanks.
Kind regards,
Suraj
Swedbank AB
SE
Hello Suraj,
To answer your question to the best of my knowledge, As a best practice for performance, evolve your Pega 7 database schema so that no classes with many saved instances or high activity are mapped to the pr_history table. Ensure that this table does not contain history instances for work items or data objects. Some applications in production may have thousands or millions of history records for high-turnover classes such as interest rates. As a best practice, create new dedicated tables with exposed columns for such classes, or add indexes to eliminate table scans and add exposed columns to avoid retrieving the Storage Stream.
You can find more on the below link:
Hope this helps.
Sincerely,
Pawan