ProjectWise Administrator Help

Truncating Audit Trail Records

When an audit trail record is generated, it gets stored in the database in the dms_audt table. You can choose to keep all audit trail records for the datasource in this one table, however, to prevent this table from getting too large, you can have the ProjectWise Design Integration Server truncate the dms_audt table. You have the following configuration options:

  • keep records of a specific type in the dms_audt table for a specific amount of time, then have them deleted from the table
  • keep records of a specific type in the dms_audt table for a specific amount of time, then have them moved to another table in the database
  • keep a fixed number of records of a specific type in the dms_audt table, then when the limit is exceeded, have the oldest records deleted
  • keep a fixed number of records of a specific type in the dms_audt table, then when the limit is exceeded, have the oldest records moved to another table in the database
Note: When audit trail truncation runs, if the move to the secondary table is unsuccessful for any reason, ProjectWise will not delete the unmoved records from the dms_audt table.
Note: You cannot access the records in the secondary table through ProjectWise Explorer. However, they can be accessed by using a database application if needed.
Note: When the option Move truncated records into secondary table is off, any audit trail records that are removed from the main dms_audt table are permanently deleted.

Once you have enabled the Move truncated records into secondary table setting and specified a secondary audit trail table, you can then configure (for each audit trail record type) whether you want to:

  • Keep all records — Records of the selected type are kept indefinitely and are never removed from the main dms_audt table
  • Keep records for a specified period — When audit trail records of the selected type have been kept for the maximum specified length of time, they are removed from the main dms_audt and moved to the specified secondary table.
  • Keep specified number of records — When the specified maximum number of audit trail records of the selected record type has been exceeded, the oldest exceeding records will be removed from the main dms_audt table and moved to the specified secondary table. If the table does not already exist in the database, it will be created as necessary when the audit trail truncation occurs.
Note: Also, if you turn on Keep all records for all record types, then you do not need to turn on Move truncated records into secondary table on the Audit Trail tab of the Datasource Properties dialog, as the server would never be truncating any audit trail records.