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.

Database column population using the Column Populator utility

Updated on September 13, 2021

After you make schema changes that expose a property as a database table column, you can update rows in a PegaRULES database table by using the Column Populator utility. For a property whose values were previously stored only in the Storage Stream (BLOB) column, the utility can populate the values for that property into a newly exposed column. You can also rebuild database indexes and Index- instances defined by Declare Index rules for the newly populated column as part of the same operation.

Typically, run the Column Populator immediately after making the database table changes, whether the changes were made with the Modify Database Schema tool or by a database administrator. Until the Column Populator finishes, data values in the table are "out of sync," because some properties might have null values when the column values are viewed, but might have non-null saved values if the BLOB column (pzPVStream) is expanded into a clipboard page.

For more information, see Database column population using the Column Populator.

  • Previous topic How to migrate work object history records that were incorrectly saved in the pr_history table
  • Next topic How to use the Column Populator utility in PRPC 6.x to Pega 7.1.9

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