Large frequently changed tables could have potential to grow very large. We do employ insert update and triggers for most of our auditing, but our history tables are on a separate history database which can be moved so it does not affect the performance and disk space of our production server as much.
~Brad -----Original Message----- From: Casey Dougall [mailto:[EMAIL PROTECTED] Sent: Monday, September 18, 2006 2:23 PM To: CF-Talk Subject: Re: SQL in a variable Personally what I like doing in this whole audit trail is just mark the data IsDeleted and then insert a new record with the new data. 4 fields are needed. IsDeleted = 1 or 0 LastModified = "TimeStamp" ModifiedBy = "UserID" LastCurrentRecord = "ID of record you just Marked IsDeleted." Now a month or year later I can go in and delete data that is just taking up space but is not needed for the audit trail anymore. Casey ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:253442 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
