About Table Auditing

Table Auditing in P6 EPPM allows you to gather information about incremental changes to projects and project-related data. If you configure table auditing, whenever a change is made in any of the tables you choose to audit, a row is written to the PAUDIT table of the database, recording information about the field that was changed, the activity and project for which the change was made, which user made the change and from which application, as well as the previous and new values of the data.

Because every change to an audited table triggers a row to be written to PAUDIT, table auditing involves an increased amount of interaction between P6 and the database, which can affect performance.

You can configure auditing on one or many tables in the database. For each table you can audit the following types of changes:

Insert: A new record is written to a table, for example, when a new item is created. Audit data for insert operations shows only a new value; the old value is null because the row represents a new row being written to the table.
Update: A record is modified, for example, when a field's value is changed. Audit data for update operations show both an old and a new value, representing the values of the field before and after the change was made.
Delete: A record is removed from a table, for example when a data item is deleted. Audit data for delete operations shows only an old value; the new value is null because the row represents a table row being removed.

Before you can see audit data, you must configure P6 EPPM to start collecting audit data and set up the Publish Audit Data job to run. See: Configuring Audit Settings

After audit data has been collected by P6 EPPM, you can view it either by running reports against the database to query the PAUDITX table, or by using the Audit panel on the EPS page of P6. See: Viewing Audit Data

To learn more about table auditing, see: P6 EPPM Database Administration Guide for On-Premises.

Related Topics