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.

Exposing too many properties as database columns can affect performance

Suggest edit Updated on September 13, 2021

Summary

A developer asks:

It is known whether performance suffers by exposing too many columns? We want to expose an additional 20 to 30 properties as individual columns in one of our database tables, mostly for reporting purpose. Do you have a recommendation for the maximum number of columns that should be exposed?



 

Suggested Approach

Exposing properties as database columns is in general a good idea, and the 20 to 30 additional columns that you propose are not likely to create a noticeable performance issue.  (Exposing properties as database columns creates copies of the properties in the Blob column; it does not delete them from the Blob.)

Anecdotally, having too many columns means that each database row becomes big and your database suffers additional processing and space overhead: The more exposed columns, and the more native database indexes you have, the more expensive the each read, update, or delete operation becomes.

Consider involving a DBA who is familiar with of the fine art of database tuning.  Going overboard by exposing hundreds of properties is probably excessive.  But significant performance degradation is unlikely with 20 to 30 new columns.

  • Previous topic Enable the UDF feature in JSP Lookup tag for best performance
  • Next topic How to compress the BLOB values in the PegaRULES database
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us