FIX: Update on View-based Cursor Fails to Modify Row if View Contains a Join

ID: Q238547

The information in this article applies to:

Microsoft SQL Server version 7.0

BUG #: 56059 (SQLBUG_70)

SYMPTOMS

An update, with a cursor that is based on a view, can fail to update a row if the view is based on a join of one or more tables. ODBC applications may encounter a SQL_SUCCESS_WITH_INFO message "Cursor operation conflict" in this situation because no rows were affected by the cursor update. If you are using an ANSI T-SQL based cursor, an UPDATE statement in this scenario fails with the following error:

Msg 16947, Level 16, State 1
No rows were updated or deleted.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Version      File name   Platform
   ---------------------------------------------------------

   7.00.721     s70721i.exe Intel
                s70721a.exe Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

WORKAROUND

Define the cursor with the query on which the view is defined.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0.

Additional query words: sp_cursor

Keywords : kbbug7.00 kbSQLServ700bug
Version : winnt:7.0
Platform : winnt
Issue type : kbbug