InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 03:11:17 GMT20http://www.sqlservercentral.com/Forums/Topic434953-259-1.aspxYou could do something like:[code="sql"] DECLARE @operation as Varchar(10); DECLARE @Count as int; SET @operation = 'Inserted'; SELECT @Count = COUNT(*) FROM DELETED; if @Count > 0 BEGIN SET @operation = 'Deleted'; SELECT @Count = COUNT(*) FROM INSERTED; IF @Count > 0 SET @operation = 'Updated' END[/code]HTH,RobWed, 12 Sep 2012 21:54:32 GMTrobert.gerald.taylorhttp://www.sqlservercentral.com/Forums/Topic434953-259-1.aspxIf your trigger is For Update, Insert there is not any system information identifying what action caused the trigger to fire.You could duplicate your code, and create 1 trigger for insert, and 1 trigger for update, or test for Existing rows as you mentioned.Wed, 19 Dec 2007 15:04:32 GMTRay Mhttp://www.sqlservercentral.com/Forums/Topic434953-259-1.aspxIs there an "easy/quick" way to determine inside the trigger itself whether it is being fired because of an Insert or because of an Update when a trigger has been defined for Insert, Update?Without inquiring whether a row exists or not, is there a system variable that can determine this?Wed, 19 Dec 2007 13:35:47 GMTbob pearson-184607