While looking at some tables in my schema, it occured to me if I could create a global audit table, which might contain some information on DML entries on all tables. I'd like to store 'Table name', 'Modifier', 'Row Update/Insert/Delete query', 'query result', 'Modifying Instance Information: sql-client, session-info(?)', performance items, timestamp, etc
. I could also limit this table-size by limiting number of rows through a insert trigger
on this table through rowcount
. Is this construct allowed? Is this a bad idea? What is the fastest it could get? What more problems does construct like this present? Basically, is direct logging into database a bad idea?
Logging DML with database level trigger
on big data and bulk insert/update/delete
have a performance issue, so there is three other option :
And i strongly preferred option no 1.