FIX: Update of Table with Large varchar Columns May Cause Access Violation

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


When you update a table that is joined to itself and that contains large varchar columns, SQL Server may generate an access violation (AV).


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

More information

The following query generates an access violation:
create table test(col1 integer, col2 varchar(8000), col3 varchar(8000))
insert test values (1, replicate('b',8000), 'c')
insert test values (2,'b', replicate('c',8000))
insert test values (3,replicate('b',8000),'c')
update test set col2 = test2.col2, col3 = test2.col3
            from test, test test2
	    where test.col1 >= test2.col1


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

Contact us for more help

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