Could not create an acceptable cursor

Question

Could not create an acceptable cursor

Viewing 11 posts - 16 through 25 (of 25 total)

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

chris.stuart SSCarpal Tunnel Points: 4965 More actions · Answer 1

Just to add; also solved my problem by adding unique non-clustered index on the lined table

TheSQLGuru SSC Guru Points: 134017 More actions · Answer 2

Have you tried to do the update directly on the server you are updating, using linked servers out to the other parts of the query?

Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service

koenwuyts Valued Member Points: 71 More actions · Answer 3

koenwuyts

Valued Member

Points: 71

September 1, 2009 at 9:39 am

#1047623

Thanks man, the unique index solved my problem!

Tim Radney SSC Veteran Points: 213 More actions · Answer 4

Tim Radney

SSC Veteran

Points: 213

February 18, 2010 at 7:42 am

#1120924

worked for me

Tim Radney SSC Veteran Points: 213 More actions · Answer 5

Unique Index Requirement

The SQL Server OLE DB provider requires that a unique index exist on the underlying table for UPDATE or DELETE operations. If no unique index exists on a remote table, the following error occurs when an UPDATE or DELETE is attempted:

Server: Msg 7320, Level 16, State 2, Line 1 Could not execute query against OLE DB provider 'SQLOLEDB'. The provider could not support a required row lookup interface. The provider indicates that conflicts occurred with other properties or requirements. [OLE/DB provider returned message: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

This applies both to OpenQuery and four-part named UPDATE and DELETE operations. The problem is resolved by adding a unique index on the remote table.

A clustered index also works.

Safi Parvez SSC Rookie Points: 37 More actions · Answer 6

Safi Parvez

SSC Rookie

Points: 37

May 21, 2010 at 2:18 pm

#1171099

Thanks! It fixed the same issue that I had.

mjstuart SSC Journeyman Points: 88 More actions · Answer 7

Hi Tim,

I have the same issue using a linked server between a SQL 2000 and SQL 2005 boxes, can you tell me if you ever resolved this issue?

Many Thanks

Marcus

modernmozart Grasshopper Points: 19 More actions · Answer 8

Solved my problem, too.

But I wonder how could it be and what if the table cannot be added a index 😉

melwyn-772312 Valued Member Points: 57 More actions · Answer 9

Hi,

We have encoutered Similar Error Updating On a Linked server from SQL2008 to SQL2000.

Error :Multiple-step OLE DB operation generated errors. Could not create an acceptable cursor

Workaround : After a Days Hard fighting at the day End I tried a trick :

On the Linked server I added a primary key on the table on which I was updating.

i.e Updating table on linked server need to have atleast one primary key

Nery Melwyn Nazareth

Sr DBA Sharekhan Ltd.

shobha.aradhya SSC Veteran Points: 256 More actions · Answer 10

Hi,

I am facing similar issue. What my confusion is previously the job was running fine. We are facing this problem since few days back. There is no change with respect any tables.

Any idea?

Thanks in advance,

Aradhya

Sunny1 SSC Eights! Points: 871 More actions · Answer 11

I have the same error - Using a linked server, UPDATE four-part remote view. Even the base table has clustered index and non-clustered unique index, it still won't work.

However, I just update the remote base table through the linked server directly, then there is no problem.