General discussion


Setting up an audit trail for SQL

By fergal.oshea ·
I've been tasked with designing an auditing system for SQL databases. It's to be implemented at a software level i.e not using triggers, but using Apache Log4j. The technologies we use include JSPs, Java, Tomcat, JBoss and MySQL.

What I'm really looking for is tips on best practice and criteria in terms of deciding how many SQL tables to set up for logging to, how big they should be, and what gets logged (and when) and what doesn't.

Any help, including links to articles, would be gratefully received.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Me too

by t1g312 In reply to Setting up an audit trail ...

Hi Fergal,

I too am looking for the exact same information. I've managed to create and pretty powerful audit trail trigger in SQL server but due to lack of experience, I am not sure which tables to audit. Do people generally audit only transaction tables or master tables too? And how about inserts/deletes/updates? Would appreciate it if someone could help us.

Thanks in advance,

Related Discussions

Related Forums