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

Slow application response after upgrade to Pega 7.1.8



User applications are migrated from PRPC 5.5 SP1 to Pega 7.1.8 and after this upgrade, the application servers were responding slow and user had to restart the application server manually.

Error Messages

No error on screen.

Steps to Reproduce

Access the application to reproduce the issue.

Root Cause

SendStringParametersAsUnicode JDBC connection property was set as false in the user’s environment.

MS SQL JDBC drivers specify a configuration property called sendStringParametersAsUnicode which helps in getting rid of this unicode conversion. This property defaults to 'true’ which makes the driver send every string in Unicode format to the database by default. If the database tables use only the ASCII data types, user MUST disable this property to ensure the following:
1) All parameters of the JDBC statements are sent to the database in ASCII format thereby getting rid of Unicode conversion overhead.
2) All indexes are actively used during data fetches thereby getting rid of whole table scans.

To disable this property, just append the property with its value as 'false' to the jdbc connection URL as shown below:


 Set JDBC connection property SendStringParametersAsUnicode to false to improve the performance.


Suggest Edit

Published March 2, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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