I'm considering different approaches to implementing history log for a user centric web application and was wondering if people have any experience with that.
I want to provide a user with a log of his actions (inserts, updates, deletes) for as many relevant tables as needed (for example, for calendar events or todo tasks).
The problem is that those log tables grow to enourmous sizes very fast (even more so than the original tables, which are very large to begin with), and become very hard to maintain.
I would love to hear some suggestions on how to tackle the implementation of those tables, both from a practical standpoint (anybody has much experience with trigger performance?), and from a maintainance standpoint (horizontal partitioning, data warehousing etc.).
Thanks!
History data tables
Moderator: General Moderators