After 14 years on Sugar our audit_events table has 31M rows!
I don't quite grasp the purpose of this table... I am wondering if this is just an audit of actions taken?
Could I delete entries that are, say, more than 6mo old?
Thanks,
Francesca
After 14 years on Sugar our audit_events table has 31M rows!
I don't quite grasp the purpose of this table... I am wondering if this is just an audit of actions taken?
Could I delete entries that are, say, more than 6mo old?
Thanks,
Francesca
Hi Francesca Shiekh ,
The audit_events table contains data about the user or process that performed an audited change within any Sugar module. If you looking in a modules *_audit table, you will find an event_id associated with each audit entry that ties to the audit_events.id value. You can prune data from audit_events, but you should only do so if you are also pruning corresponding data from the relevant module-level audit tables.
Chris
Hi Francesca Shiekh ,
The audit_events table contains data about the user or process that performed an audited change within any Sugar module. If you looking in a modules *_audit table, you will find an event_id associated with each audit entry that ties to the audit_events.id value. You can prune data from audit_events, but you should only do so if you are also pruning corresponding data from the relevant module-level audit tables.
Chris
