However, you can associate a child class with a table that is different from its parent by creating a separate Data-Admin-DB-Table instance for the child. This may be desirable for performance, backup, space, or other reasons. The table that you specify for a child class overrides the table defined for the parent class.

For example, the standard schema places instances of the Data-Party-Com class — which identify business entities — in the pr_data table, using the Data-Admin-DB-Table instance named Data-. If your application includes thousands or millions of such records, consider placing them in a dedicated table. To make a dedicated table (using this example):

1. Using database tools, create a table (call it myco_businesses) within the Pega database.
2. Make sure that the schema includes the properties needed for every table, and that property pzInsKey is identified as the primary key using a database constraint.
3. Identify additional columns for other properties to be exposed.
4. Move all rows of the pr_data table that have Data-Party-Com as the value of the pxObjClass column into the new table.
5. Add a Data-Admin-DB-Table instance named Data-Party-Com that references the myco_businesses table.
6. Run the Column Populator utility to populate values for exposed columns from the BLOB column (Storage Stream).