Audit Trail Table

[Robert2150]

I have a database with many users, I am considering adding an Audit Trail table to track record changes. I am concerned that due to the amount of activity in the database it may become "bloated" very quickly. Any suggestions on how to manage this to prevent the table from getting too large?

[June7]

What is 'too large'? Maybe archive records to another db. Maybe delete records of a certain age or after reviewed.

[Robert2150]

The database is not on SQL, and has a 2 GB size limit. Either of your suggestions could be an answer, can either process be automated?

[Micron]

If you only care that a record was edited because you have nightly network backups for making comparisons, then you would only need an update field of date type (such as Status_Update) to ID the altered records. Here is an approach you should check out: http://allenbrowne.com/appaudit.html