David Ziffer (10/21/2012)
Sorry if this is a multiple post, but I tried responding once and it didn't post. I never did follow up further on this single-audit-table approach to auditing, since it is of somewhat limited use (reconstructing data using this mechanism would be pretty complex). I did write another article series on this site, however, entitled "Writing Nearly Codeless Apps", which discusses a much more practical and comprehensive auditing mechnism that allows you to easily recall every row of every table of an application as of a given date.
Nice, short and sweet artcle. However, between the more than doubling the size of the database just for the inserts and saving a full row even if only one column got updated, I have to say that you must have a huge amount of disk space available. Backups and restores will suffer, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.