Working with the PegaRULES database
System tables

Seventeen PegaRULES database tables contain instances of concrete classes derived from the System- base class: These tables typically contain only a few rows with high turnover.

Seventeen tables can store instances of classes derived from the System- base class.

Do not alter the mapping, schema, or structure of these tables except as advised by Pegasystems support staff.

Table	Description
pr_page_store	Contains rows corresponding to instances of the System-SavedPages class. When a user session times out, the system saves a user's entire thread context automatically in this table, until that user completes a log-in challenge or an expiration timeout occurs. ERNSG 12/8/05 The system automatically deletes rows of this table that are more than three days old.
pr4_rule_sysgen	Contains instances of the System-CachedConclusion class.
pr_sys_cache_dep	Contains instances of the System-Cache-Dependency class, maintaining facts used in internal operations, supporting rules assembly and the static assembler. V6.1
pr_sys_cache_entry	Contains instances of the System-Cache-Dependency class, maintaining facts used in internal operations, supporting rules assembly and the static assembler. V6.1
pr_sys_cache_impl	Contains instances of the System-Cache-Dependency class, maintaining facts used in internal operations, supporting rules assembly and the static assembler. V6.1
pr_sys_context	Contains rows corresponding to instances of the System-Requestor-Context class, for passivated requestors.
pr_sys_decchg	Contains rows corresponding to instances of the System-Declare-Changes class, to support execution of declarative expression rules. PROJ-30 5.3
pr_sys_locks	Contains rows corresponding to locks held, instances of the System-Locks class. Supports the Locks report, available from the Designer Studio View > System > Locks menu selection.
pr_sys_queues	Contains rows for queued service requests from concrete classes such as System-Queue-DefaultEntry, derived from the System-Queue- abstract class, except for classes explicitly mapped to another table.
pr_sys_queue_execreq_conn	Contains rows for queued connector requests, instances of concrete classes derived from the System-Queue-ExecutionRequest-Service- class. About Connector Request Processor data instances.PROJ-911
pr_sys_queue_execreq_svc	Contains rows for queued service requests, instances of concrete classes derived from the System-Queue-ExecutionRequest-Connect- class. About Service Request Processor data instances.PROJ-911
pr_sys_queue_sla	Contains rows for instances of the System-Queue-ServiceLevel class, supporting event-driven processing of service level deadlines and goals by the Pega-ProCom agent. Understanding the Pega-ProCom agent. NOT pr_sys_queue-servicelevels
pr_sys_queue_startflows	Contains rows for starter flows, reflected in instances of the System-Queue-StartingFlows class. Facilitates fast operation of the dropdown list of starting flows by application on application portals. V6.1
pr_sys_statusnodes	Contains one row for each participating node in the system, corresponding to instances of the System-Status-Nodes class. This table occasionally can contain apparently duplicate rows, because the true key is based on an encrypted form of the node name, system name, and path of the temporary directory. Run the RemoveOldNodes activity to purge rows corresponding to nodes that have been inactive for at least 24 hours. SR-993
pr_sys_updatescache	Contains one row for each change to the rules since the most recent pulse processing by the PegaRULES agent. These rows correspond to instances of the System-Updates-Cache class. This table is scanned by a trigger when rules are updated and added to the cache; it is emptied when cache processing completes. SR-1023 PRKB-20378 B-16917B-21153 See Understanding the PegaRULES agent.
pr_sys_workindexer_queue	Contains rows of the System-Work-Index class, identifying work objects that need re-indexing for full-text search.
pr_sys_user	Contains one row for each rule delegation, corresponding to instances of the System-User-MyRules class.

The database table pr_portal_state holds instances of the two classes Pega-Portal-Developer and Pega-Portal-User, which contain saved information about portal use by each connected user.

	passivation, referencing rules, timeouts
	Atlas — Initial Database Table data instances Atlas — Standard classes derived from the System- base class

Working with the PegaRULES database