Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Large property value storage

Updated on May 15, 2018

Pega® Platform does not restrict the length of property values. However, you can set the size limit for a property value by setting the Max length field on the Advanced tab of the Property form. Long properties, especially if you have thousands of them in memory, can affect performance, including memory and database traffic. The JVM memory limit for the system must be large enough to handle the number of long properties that are processed.

In addition to performance considerations, you might not be able to expose properties with long values as database columns, depending on your database software's aggregate size limit for exposed columns. If a property exceeds your database's aggregate size limit, making the property too long to expose as a database column, consider dividing the property and storing it as a number of shorter properties.

If your property is exposed, set the property value size in the Max length field to equal the maximum size of the database column to ensure that your data fits into the column.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us