BUG: UPDATE to View with Cursor May Cause Handled AV

 Last reviewed: January 22, 1998
Article ID: Q179351
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 17744 (6.5)

SYMPTOMS

An UPDATE of a view WHERE CURRENT OF a cursor may cause a handled access violation (AV), which stops the client thread on the SQL Server. This problem can occur if all of the following conditions are true:

  • The view joins three or more tables.
  • The innermost join condition is based on multiple columns.
  • The column updated is from the innermost table.

WORKAROUND

To work around this problem, do either of the following:

  • Change the WHERE clause of the UPDATE statement so that it does not use the CURRENT OF <cursor> clause.

    -or-

  • Declare the cursor on the underlying tables instead of on the view.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: av violation prepscan
Keywords : kbbug6.50 SSrvGPF SSrvTran_SQL
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround

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: January 22, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.