Question

1
Replies
29
Views
ArjanM04 Member since 2014 39 posts
Achmea
Posted: March 27, 2019
Last activity: March 27, 2019
Closed

Inefficient OOTB Report definition causing performance issue , SA-47747

Hi All,

Is this ( https://community.pega.com/support/support-articles/inefficient-ootb-report-definition-causing-performance-issue ) article also applicable to Pega 7.3.1?

Our DBA sees the same queries causing issues (PEGA0005 messages from over 5 seconds) in our 7.3.1 environment, but can't follow up the instructions mentioned within that document as when using the INCLUDE option, it must become a UNIQUE index with DB2, but that is not possible because duplicate keys would then arise.

Or do we need to do something different?

Kind regards,

Arjan Maus

***Edited by Moderator: Pallavi to update platform capability tags and SA Details***

Pega Platform System Administration Reporting
Moderation Team has archived post
Share this page LinkedIn