How about some details on the audit trails themselves?

First, you can configure the audits from multiple audited tables to be written to one or more audit trail tables.  We believe it is easier to have a single audit trail table, for easier operations and to have a single source for reporting.  However, this it is a customer decision at implementation time.  Of course, you could change at any point; you’re not locked in.

The audit trail table stores all change details from all of the related audited tables for efficient and flexible reporting:

  • Column Before and After
  • Table Primary Key columns and values
  • Table and Column names
  • Trigger Action (Insert, Update, or Delete)
  • When the column changed and Who changed it
  • Session Details like IP Address, OS User, Session ID, and Commit ID
  • Other column values within the same table at time of change, for context
  • Selected data values from other tables captured at the exact time of the transaction, again for context.  An example is where you audit an order, and save the Customer ID from the audited table, but look up and also store the Customer Name from the Customer Master table