Some Important Pega PRPC database tables

Following are some general pega rules database tables which are used to store different objects :-

pc_assign_worklist:
 
It is used to store worklist related assignments

pc_assign_workbasket:

Work basket related assignments are stored in this table.

pc_work:


It is a default table in pega to store work objects. This behavior can be customized to use a user defined table to store work objects.
Steps to follow for customization:-
1. Copy the pc_work table schema  and modify the table name
2. Change the class group mapping (Data-Admin-DB-Table) to the newly created table.

pc_data_workattach:

Store work objects attachments i.e. files, screenshots etc.

pc_history_work:

It is used to store work objects history.

pr_data:

Default table for data instances.
 
 
pr_operators:

Store the Data-Admin-Operator-ID instances
 

p.s.:- All the PegaRULES database tables have two very important common columns, pxObjClass and pzInskey. 

pzInsKey:

pzInsKey is called the handle for an instance because it is a unique column for each instance which store the key with exact modified date.

pxObjClass:

The pxObjClass column, present in every table, identifies the Process Commander class of the row. When committing an instance of a concrete class to the PegaRULES database, the system uses the pattern inheritance algorithm to find the table name.

Reference: Pega Community