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

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Jan 31, 2018
Last activity: Jan 31, 2018
Posted: 31 Jan 2018 9:43 EST
Last activity: 31 Jan 2018 16:10 EST
Closed

SELECT TOP - Long Running Queries - review and recommendations.

Hi Team,

We could find a lot of "SELECT TOP " Long Running Queries in our environments.

PFA for the queries.Please help.

To see attachments, please log in.
System Administration
Data Integration

Posted: 6 years ago
Posted: 31 Jan 2018 16:10 EST
Ankur Das (@nkur.das_GCS) Principal Software Solutions Engineer
Pegasystems Inc.
US

Hi,

SQL queries in the attached xlsx are related to Rule ABA Cache population. In other words, the ABA cache was being primed for the first time after you did an application deployment or upgrade. Once the cache is primed you should not be seeing these PEGA0005 Alerts for the same queries. 

The magnitude/impact of the queries in terms of time taken to execute is not considerably high than the OOTB threshold of 500ms. However, if you would like to improve the query execution times, it is recommended to update the statistics explicitly of the following tables on a periodic basis.
 
pr_sys_app_hierarchy_flat
pr_sys_app_ruleset_index
pr4_rule_vw
pr_sys_appcache_dep
pr_sys_class_ancestors
 
SQL:- UPDATE STATISTICS <schema>.<table_name> WITH FULL SCAN

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