Contradictory information in the topcis for SAVE and ROLLBACK TRANSACTION - by Erland Sommarskog

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 852418 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/13/2014 1:18:10 PM
Access Restriction Public


The topic for SAVE TRANSACTION says:

When part of a transaction is rolled back to a savepoint, resources continue to be held until the completion of the transaction or a rollback of the complete transaction.
But the topic for ROLLBACK TRANSACTION says:

A ROLLBACK TRANSACTION statement specifying a savepoint_name releases any locks that are acquired beyond the savepoint, with the exception of escalations and conversions. These locks are not released, and they are not converted back to their previous lock mode.

I did some quick test that indicated that locks could indeed be released when rolling back to a save point.
Sign in to post a comment.
Posted by Erland Sommarskog on 6/21/2014 at 3:37 AM
I can see the change (as well as the fixed to the other doc bugs I recently filed for transaction-related statements) on the web. However, when I install the latest updates to the downloadable version (which is the one that counts in my book), the changes are not there?
Posted by Microsoft on 4/15/2014 at 3:34 PM
Confirmed and fixed. SAVE now reads the same as ROLLBACK. Fixed in SQL Server 2012 and SQL Server 2014. Will appear as each doc set is refreshed. Thanks. Rick Byham
Posted by Microsoft on 4/15/2014 at 9:43 AM
Hi Erland. Thank you for submitting this. I'll test that to perform due dilligence, and then copy the ROLLBACK text into SAVE topic.