Sybase optimizer creates a cursor for a DELETE query which then fails?

When using the delete target table in a from clause don't put an alias on it DELETE archive_table FROM archive_table, #arc_chunk loc WHERE archive_table. Col = loc. Col EDIT Another possibility is to remove the need for a join and fold it all into the where clause DELETE archive_table WHERE EXISTS ( SELECT 1 FROM #arc_chunk loc WHERE archive_table.

Col = loc. Col ) I am assuming that 'col' is the unique key for the row.

When using the delete target table in a from clause don't put an alias on it. DELETE archive_table FROM archive_table, #arc_chunk loc WHERE archive_table. Col = loc.

Col EDIT Another possibility is to remove the need for a join and fold it all into the where clause. DELETE archive_table WHERE EXISTS ( SELECT 1 FROM #arc_chunk loc WHERE archive_table. Col = loc.

Col ) I am assuming that 'col' is the unique key for the row.

Nope... same problem. Except the cursor has now changed to 'C63172' :-( – Dylan Piergies Jul 30 '10 at 13:36.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.