I'd do a little as possible. The trigger code will be execute for each appropriate statement (INSERT, UPDATE, DELETE) no matter how many row are modifed (even zero) or what columns are modified.

-Mike

>Is there a recommendation as to how much is too much code to have in a trigger? For instance, if I need handle a bunch of conditional coding should that be handled in a trigger or is there a better place to do that?
>
>I've heard some SQL Server users that never use triggers at all.