• It would have basically the same effect as a cursor in a stored procedure. The difference is, the trigger fires every time the specified database operation (INSERT, UPDATE, or DELETE) is performed on the table. So if you have a lot of operations against a given table, that trigger is going to fire a lot of times. That's typically why anything complex should be avoided in triggers if possible.

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley