Most of the tables that support auditing have multiple indexes. When enabling auditing, you have the option of activating all the indexes, or only the primary indexes. Generally, only the primary indexes should be activated in a production database. The non-primary indexes are used for reporting and should be enabled in your archive database. The table below lists the indexes for each of the auditing-related schema tables. See OpenEdge Getting Started: Core Business Services - Security and Auditing for details on the components of each index.

Table 1. Indexes for auditing schema tables

Table	Index name	Index type
_aud-audit-data	_AppContext-Id	–
	_Audit-time	–
	_Connection-id	–
	_Data-guid	Primary, Unique
	_Event-context	–
	_Event-group	–
	_EventId	–
	_Userid	–
_aud-audit-data-value	_Field-name	–
	_Continuation-seq	–
_aud-audit-policy	_Policy-active	–
	_Policy-desc	–
	_Policy-guid	Primary, Unique
	_Policy-name	Unique
_aud-event	_Event-desc	–
	_Event-id	Primary, Unique
	_Event-name	–
_aud-event-policy	_Event-guid	Primary, Unique
	_Event-id	–
_aud-field-policy	_Field-name	Primary, Unique
	_File-field-owner	–
_aud-file-policy	_Create-event-id	–
	_Delete-event-id	–
	_File-owner	–
	_Guid-file-owner	Primary, Unique
	_Read-event-id	–
	_Update-event-id	–
_Client-session	_Auth-time	–
	_Db-guid	–
	_Session-uuid	Primary, Unique
	_Userid	–
_Db-detail	_Db-guid	Primary, Unique