I would add that triggers tend to "slip through the cracks" when making changes. You have to remember to analyze what any change in the db schema or data might do to a trigger.
-Mark -----Original Message----- From: Robertson-Ravo, Neil (RX) [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 11, 2005 6:22 AM To: CF-Talk Subject: RE: [OT] SQL Audit with CF - or maybe triggers? You could use Triggers yes, but it is not advised. Triggers can be very detrimental to performance as table size increases. If you are using SQL Server it is probably better to go for a Stored Procedure solution. N -----Original Message----- From: Michel Deloux [mailto:[EMAIL PROTECTED] Sent: 11 May 2005 12:00 To: CF-Talk Subject: [OT] SQL Audit with CF - or maybe triggers? Hi all I'm a CF newbie and look for any sort of help for my application. How to audit update and delete operations in our DB? I have try to use trigger but how to pass parameters for triggers like userID, fields changed, etc? Do you have any example about how to do that? Cheers Michel Deloux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:206335 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
