Discussion2Replies253Views×Close popoverSudhanshu Singh (SudhanshuS5799) Cognizant Technology Solutions Cognizant Technology Solutions ES View Profile SudhanshuS5799 Member since 2014 4 posts Cognizant Technology Solutions Posted: May 13, 2016Last activity: April 6, 2018Posted: 13 May 2016 9:08 EDTLast activity: 6 Apr 2018 19:26 EDT Closed DB issue after upgrading to Pega 7.2A long query of approx 5500 lines is running on pr_index_reference table after upgrade which makes the server very slow.What could be the reason?**Moderation Team has archived post**This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post. System Administration Upgrades ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion. Posted: 4 years agoPosted: 22 Jun 2016 2:45 EDT×Close popoverDhevendra Earva (earvd) PEGA Senior Manager, Cloud Engineering Pegasystems Inc. IN View Profileearvd PEGA replied to SudhanshuS5799Did you run the rebuild indexes stored procedure after the upgrade?. This is one of the root cause for slow running query. Posted: 4 years agoUpdated: 4 years agoPosted: 23 Jun 2016 4:48 EDTUpdated: 23 Jun 2016 4:49 EDT×Close popoverVigneshwaran Aravindhan (VigneshAravind) Cognizant Senior Technology Architect Cognizant IN View ProfileVigneshAravind Cognizant replied to SudhanshuS5799Run RULES_SCHEMA.SPPR_REBUILD_INDEXES to rebuild the indexes. After this verify the PegaAlertLogs for any alerts from pr_index_reference table. Please let us know if this helped.