Post reply

Cursor Errors

  • October 1, 2007 at 7:55 am

    #76790

    When I ran trace for one of the application on which users are complaining about slowness, I found the following errors,

    Error: 16945, Severity: 16, State: 1

    Error: 16937, Severity: 16, State: 1

    Error: 16954, Severity: 10, State: 1 --- This one repeated like 20 times in a 30seconds trace.

    Are these should be worried about? I know these are application related SQL cursor errors, but would like to know why these are caused as i couldn't get proper answer from searching google.

    Will these errors effect performance?

  • October 1, 2007 at 8:26 am

    #737716

    select * from master.dbo.sysmessages where error = 16945

    select * from master.dbo.sysmessages where error = 16937

    select * from master.dbo.sysmessages where error = 16954

    error = 16945: The cursor was not declared.

    error = 16937: A server cursor is not allowed on a remote stored procedure or stored procedure with more than one SELECT statement. Use a default result set or client cursor.

    error = 16954: Executing SQL directly; no cursor.

    lookslike the cursor was not declared in some code, and is resulting int he errors you are seeing.

    can you track down what is calling the code?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • October 1, 2007 at 3:31 pm

    #737920

    this is just another reason to get rid of cursors ... 😀


    * Noel

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

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