Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Users are experiencing extreme slowness after Pega 7 upgrade



Users are experiencing extreme slowness after Pega 7 upgrade.

Error Messages

For the slowness, occasional database deadlocks detected: Transaction (Process ID 216) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Steps to Reproduce


Root Cause

The root cause of this problem is in a third-party product integrated with PRPC. Report defintions which return many rows (using join against many tables) were causing lock escalation within the SQLServer DB, which led to deadlocks.


This issue is resolved by making the following change to the PRPC operating environment: Configuration within the DB was changed to use a different isolation level READ_COMMITTED_SNAPSHOT which prevents the lock escalations that led to deadlocks.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us