XPost: microsoft.public.sqlserver.programming   
   From: genew@ocis.net   
      
   On Thu, 3 Mar 2011 02:27:37 +0000 (UTC), Erland Sommarskog   
    wrote:   
      
   >Gene Wirchenko (genew@ocis.net) writes:   
   >>      Thank you.  And what about when the underlying data gets   
   >> modified?   
   >   
   >An INSTEAD OF triggers fires instead of the INSERT/UPDATE/DELETE/MERGE   
   >statment that fired the trigger, and you need to resubmit the statement   
   >if you want to carry out the modification.   
   >   
   >FOR and AFTER triggers fires after the modification has taken place, and   
   >constraints have been validated. By default, if there is an error in the   
   >trigger, this rolls back the entire statement, even if there was no explicit   
   >transaction.   
      
        If I understand you correctly, then this covers my main concern:   
   atomicity of the whole operation.   
      
        Thank you.   
      
   Sincerely,   
      
   Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)