FIX: Incorrect Locking with a Dynamic Cursor FETCH LAST Operation and a Serializable Transaction

Article translations Article translations
Article ID: 224998 - View products that this article applies to.
This article was previously published under Q224998
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55014 (SQLBUG_70)
Expand all | Collapse all


Phantom insertions are allowed when a server-side dynamic cursor performs a FETCH LAST operation within a serializable transaction.


Use a static, forward-only, or keyset-driven cursor instead of a dynamic cursor.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 224998 - Last Review: November 2, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbcodesnippet kbfix KB224998

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from