FIX: Cursor Fetches Duplicate Row After Positioned Update

A dynamic cursor on a table without a unique index re-fetches the current row after a positioned update that uses the Transact-SQL UPDATE WHERE CURRENT OF <cursor> syntax.

To work around this behavior:

• Avoid using a dynamic cursor.
  
  -or-
  
  
• Create a unique index for the table on which the cursor is based.

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in the Post Service Pack 5a Update for Microsoft SQL Server version 6.5. To install the Post Service Pack 5a Update, you must have either SQL Server 6.5 SP5 or SP5a installed.

For information about how to download and install the SQL Server 6.5 Service Pack 5a, refer to the following article in the Microsoft Knowledge Base: If you already have SQL Server 6.5 SP5 or SP5a installed, you can download the Post SP5a Update from the following article in the Microsoft Knowledge Base: For more information, contact your primary support provider.