Auditing Attempted Transactions / No Duplicate Journaling
There seems to be little point to journal audit db updates; why rollback an audit entry for an attempted update?
I’m working on some auditing code and I have a few questions (feel free to respond regarding 2016.1 or later).
- I’ve noticed that there is little point of journaling updates to an audit database, as the Audit log is essentially an additional journal. Is there any reason not to disable journaling for audit log updates?
- I’d like to audit even transactions that get rolled back, preferably with information that the rollback occurred (this could be a second audit entry). Is there a way to get notification of a rollback that would work for both auditing of SQL and Objects transactions?
- If I do disable journaling (within a transaction), and a rollback occurs, how can I prevent ROLLFAIL errors?