FIX: Rollback of Transactions Named as Empty String Cause Access Violations

This article was previously published under Q260254
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57428 (SQLBUG_70)
Symptoms
When a transaction with a transaction name that is an empty string (that is, ' ') is rolled back, the connection or spid leaves the transaction open. For example:
create table mytab (col1 int primary key)goinsert into mytab values (1)godeclare @x varchar(10)set @x = ''begin traninsert into mytab values (1)rollback tran @xgo				
When you try to commit or rollback the same transaction in the same spid oryou close the connection or kill the spid from another connection, the spid with the open transaction causes an access violation with a fatal exception, which results in a server down.
Workaround
Do not use an empty string as a transaction name.
Status
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.
AV rollback transaction empty string
Properties

Article ID: 260254 - Last Review: 11/02/2013 02:07:00 - Revision: 3.0

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB260254
Feedback