From: esquel@sommarskog.se   
      
   Anton Shepelev (anton.txt@gmail.com) writes:   
   > Thank  you  for the replies, Erland and rja.  I have   
   > found what I think is an ambiguity in the documenta-   
   > tion:   
   >   
   >   Locks  placed  on  a  resource are associated with   
   >   either the current transaction or the current ses-   
   >   sion.   
   >   
   > where  the notion of "current transaction" is rather   
   > unintuitive, for it refers not to the scope  of  the   
   > immediate  enfolding  BEGIN  TRAN  block, but to the   
   > outermost one.  The following code:   
   >   
      
   There isn't really any ambiguity, because there is only one transaction.   
   The inner BEGIN TRANSACTION does not start any new transaction, but   
   only increases @@trancount. In the same manner, the first COMMIT in your   
   example only decreases @@trancount, but nothing is actually committed.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)