Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Arjan Maus (ArjanM04) Achmea
Achmea
NL
ArjanM04 Member since 2014 48 posts
Achmea
Posted: Mar 27, 2019
Last activity: Mar 27, 2019
Posted: 27 Mar 2019 7:43 EDT
Last activity: 27 Mar 2019 10:56 EDT
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***

To see attachments, please log in.
Pega Platform System Administration Reporting

Posted: 5 years ago
Posted: 27 Mar 2019 10:56 EDT
Laurence Brannigan (LaurenceB_GCS) PEGA Senior Software Solutions Engineer
PEG
GB

You're probably best to get your DBA's input for the specific syntax.

I'm not sure what database the SQL was written against, but I think the implication is you need to add non-unique composite indexes for those tables.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice