Error 16943

  • Hi,

    The message 16943 (Could not complete cursor operation because the table schema changed after the cursor was declared) is ocurring many times at the user application.

    How to trace it??

    Thanks

    Claudine

  • This was removed by the editor as SPAM

  • Have you tried SQL Profiler or Trace Flags?

    Marty

  • A client of ours received this error as well.  It was during an optimization.  Everything I can find would pin it on teh off chance that the index was dropped for the optimization job after the cursor was prepared but before it executed.  We have not seen it again to my knowledge.  I beleive it was an off chance rarity.  Have you encountered this error often?

  • Im seeing the same thing, over and over again. Some where on microsoft site I seen that it was an issue with SQL Server 7.0 and the possibility that Service Pack 1 had fixed it.

    H.

  • In my environment the error is reproducable on SQL 2000 SP3 + WS2003 SP1.

    During an update of a huge table (100M records) in a loop within a stored procedure the statement

    update item_word set realWordID = @realWordID where current of cur_item_word

    results in 16943. Also the counter of last updated record is > total number of records in the table being updated.

     

     

  • Hi!

    I've got the same error, but in a specific situation as follows:

    I had a cursor to a table which I was planning to change a column during the cursor execution. My ALTER TABLE statement was placed some lines after the OPEN CURSOR statement, between the FETCHs and the OPEN CURSOR. Moving the alter table statement to be executed before the OPEN CURSOR solved this problem, but I didn't find a way to change the table during its cursor execution...

  • Try to use static Keyword. "Declare Cursor Static For"

    in my case it worked.

Viewing 8 posts - 1 through 7 (of 7 total)

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