User auditing with DAAB

Topics: Data Access Application Block
Jun 5, 2012 at 5:19 AM

Hello Team,
 
I want to use EntLib 5.0 Data Application block in my SIlverlight 5+RIA application.
I want to maintain an Audit trail of user DB transactions. One idea is to customize DAAB so that each database insert/update/delete call besides making an entry in main table also makes an entry in audit table as well.
 
Thoughts/Pointers?

Thanks

Sameer

 

Jun 6, 2012 at 12:26 AM
Edited Jun 6, 2012 at 12:27 AM

Modifying the block would be one way to achieve auditing.  Others ways that I've seen are:

  • Write a facade around the DAAB to perform the requested action and audit it
  • Database Triggers
  • CallHandlers on the methods/classes that perform database actions
  • Event Sourcing appears that it is becoming a popular method to capture application state changes

Which one is best?  As in most things it depends (e.g. existing application design, time, inclination, politics/standards, etc.).

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com