But you are correct, a trigger itself may not be an overhead but the complexity within it.
-----Original Message----- From: Jochem van Dieten [mailto:[EMAIL PROTECTED] Sent: 18 August 2005 15:49 To: CF-Talk Subject: Re: @@Identity returns excessive records Robertson-Ravo, Neil (RX) wrote: > As for overhead on say an update - you perform a BULK update on a table with > an audit trigger - it can lead to serious memory issues and performance > problems as it runs each and every time. So use a statement trigger instead of a row trigger. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:215625 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
