Cursors and DTS
Tech-Archive recommends: Fix windows errors by optimizing your registry
Hi, I am using a cursor inside a stored procedure to do some complex work on
each row in a table.
Looking at the execution plan everything looks fine (Always worry about
cursors!!) and the Stored Procedure runs fine if I call it via Query
Analyser.
When I go to run the stored procedure from a DTS package (exec
MyStoredProcedure) I receive the following error message..
"The cursor is not open. Could not complete cursor operation because the set
operations have changed since the cursor was declared"
Any ideas how I can get around this??
TIA
Mark
.
Relevant Pages
- Re: noise words, @@ERROR, and stop and resume indexing
... these words at the beginning before sending them to the cursor. ... Looking for a FAQ on Indexing Services/SQL FTS ... >>Create table Noise ... >>> 1) check noise words inside stored procedure ... (microsoft.public.sqlserver.fulltext) - Re: Error adding command properties for stored procedure call
... I see you are using the SQL Native Client for SQL Server ... A server cursor is not allowed on a remote stored procedure or stored ... The stored procedure called is a test one that simply SELECTs the name field ... int InitializeAndConnect; ... (microsoft.public.data.oledb) - Re: SQL stored procedure not working.
... If I do not use that, how can I get the total record count? ... >> I create a stored procedure and a asp page. ... Even if you could specify the cursor type there, ... > interested in the RETURN value, you do not need to use a Command object. ... (microsoft.public.inetserver.asp.db) - Re: Error adding command properties for stored procedure call
... Microsoft OLE DB Provider for SQL Server ... properties to the command the execute call attempts to create a cursor. ... A server cursor is not allowed on a remote stored procedure or stored ... (microsoft.public.data.oledb) - Re: Case statement issue
... except with a cursor other than the default ... > I have taken the sample of paging using a stored procedure from the ... > case statement, then the error message. ... > The for loop also seems to be a problem. ... (microsoft.public.inetserver.asp.general) |
|