FIX: Delete/Rollback May Cause AV on Table w/Text Col & Triggers

 Last reviewed: June 27, 1997
Article ID: Q165857
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16719

SYMPTOMS

Issuing a delete statement on a table from within a transaction, followed by a rollback may cause access violations (AVs) and a variety of errors including error 840, 826, and bufwait timeouts. The server may stop responding. Sometimes SQL Server will not shut down after this problem occurs, and you need to cycle Windows NT Server to recover SQL Server. This problem will only occur if both of the following conditions are true:

  • You have a table that has at least one text column.
  • You have a delete trigger that deletes further rows in the same table.

These symptoms may vary on different hardware platforms, but when exposed to this error, an AV is always generated.

WORKAROUND

To work around this problem, do any one of the following:

  • Remove the delete trigger from the table in question.
  • Remove the delete statement from within the user-defined transaction.
  • Change table schema so that it does not require any text columns.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Keywords : kbbug6.50 SSrvGen SSrvGPF
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.