|
Posted by Erland Sommarskog on 06/04/07 21:15
Seribus Dragon (Seribus.news@seribus.com) writes:
> Why not just break up the action into three triggers? if there is
> common code use a stored procedure got that part.
That can be problematic, if you need to refer to the inserted/deleted
tables, which you often do in triggers.
Most of my triggers are for INSERT and UPDATE, but I have a couple
that are for all three actions.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|