Cursor error when running 2000 db in 2005

  • My user uses an application that is about to become obsolete. Therefore, getting the vendor to modify code is not an option. He is currently running on SQL Server 2000 on old hardware. I migrated his database to 2005 and used a compatibility of 80 (SQL Server 2000 DB engine). He was able to log in, but when he started using his application, he was immediately thrown the following error:

    "DB Error Code: 16966

    DB Error Message: sp_cursoropen: Specified concurrency control option 4 (OPTIMISTIC) is incompatible with static or fast forward only cursors. Only read-only is compatible with static or fast forward only cursors."

    I don't want to modify the way the whole server handles cursors (as suggested in sp_configure) as it holds my 2005 production databases. Does anyone know of a work-around that might solve this issue?

    Thanks!

  • BTW, I am running SQL Server 2005 SP3.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply