If we want to use after insert/update/delete triggers to log audit records into shadow tables, is there a way to find out if there will performance impact without developing the code?
The transactions are light volume in general. However we do have some transactions (once per month) that will insert 30,000 ROWS into a table. most other transactions are insert or update one ro few rows.
It sounds to me that we have to develop the trigger and run the transactionswithout auditing trigger and with trigger to see if there is any degredation in performance.