• I dont think you want a trigger - that could be an extremely long running transaction. A better/simpler approach is to save the changes in a separate table, once you get the approval, run the final update. Or decide that maybe you're better off to make the change and send the notification afterward, that way if the change is incorrect/incomplete they'll know they need to make a second change.

    Andy

    http://qa.sqlservercentral.com/columnists/awarren/