How to Audit Database Activity without Performance and Scalability Issues?

Posted by GotoError on Stack Overflow See other posts from Stack Overflow or by GotoError
Published on 2008-09-15T22:15:59Z Indexed on 2010/04/10 6:53 UTC
Read the original article Hit count: 179

Filed under:
|
|
|

I have a need to do auditing all database activity regardless of whether it came from application or someone issuing some sql via other means. So the auditing must be done at the database level. The database in question is Oracle. I looked at doing it via Triggers and also via something called Fine Grained Auditing that Oracle provides. In both cases, we turned on auditing on specific tables and specific columns. However, we found that Performance really sucks when we use either of these methods.

Since auditing is an absolute must due to regulations placed around data privacy, I am wondering what is best way to do this without significant performance degradations. If someone has Oracle specific experience with this, it will be helpful but if not just general practices around database activity auditing will be okay as well.

© Stack Overflow or respective owner

Related posts about database

Related posts about Performance