@AlekhyaP16661996

I kindly request that you do a database backup before you execute the delete queries on the tables below. 

Truncate tables if possible, so it will be clean. If not, ensure all the references are deleted in other tables to prevent orphan records.

1. Assignment tables

• pc_assign_workbasket: This table holds assignments in work queues and instances of the Assign-Workbasket class.
• pc_assign_worklist: This table holds assignments on worklists (Assign-Worklist class).
• pr_assign: This table holds external assignments (Assign-External class), which use the directed web access feature and assignments of all other types. Assignments in the Assign-Corr and Assign-Service classes are also stored as rows in the pr_assign table.

2. Data Object Tables

• pr_operators: This table contains rows corresponding to instances of the Data-Admin-Operator-ID class.
• pc_data_uniqueid: This table corresponds to the Data-UniqueID class. It contains a single row for each work item ID format in use. It records the most recently assigned work item ID of that format.
• pc_data_workattach: Attachments to work items are instances of concrete classes derived from the Data-WorkAttach- class and linked to this table.
• Custom Data tables for your application. 

3. History tables

• pc_history_work: This table contains all classes derived from the History-Work- class.

4. Case tables

• pc_work: This table saves the case instances of concrete classes derived from the Work- base class.

Link Tables: This type of table stores information about paired object instances. In the Pega Platform database, the names of link tables start with the values pc_link or pr_link.

Index Table: Most Pega Platform DB tables that support indexes have table names that start with pr_index or pc_index and fall under this category.