Post reply

SQL Profiler

  • May 6, 2003 at 9:14 pm

    #58964

    When running SQL Profiler, I'm getting the following EXCEPTION:

    Error: 16954, Severity 10, State: 1

    Any idea what this is?

  • May 7, 2003 at 3:22 am

    #456366

    Where are you seeing this?

    The message related to that is "Executing SQL directly; no cursor."

    Edited by - antares686 on 05/07/2003 03:22:47 AM

  • May 11, 2003 at 8:26 pm

    #456776

    I am seeing this in SQL Profiler. Where can I see what these errors mean and what, if anything, should be done to correct them?

  • May 15, 2003 at 5:06 pm

    #457382

    You can start in Books On-Line (the SQL Server documentation). It lists all the error numbers, severity levels, etc.

    That being said, BoL frequently only scratches the surface. You can almost always find more information by running a search on Google.com.


    David R Buckingham, MCDBA,MCSA,MCP

  • May 19, 2003 at 1:07 pm

    #457686

    Use the following one to get the exact SQL Statement running on the server, if you cant use Profiler

    Exec xp_sqltrace Trace, @EventFilter = 115, @Fulltext = 1

    Edited by - shastryv on 05/19/2003 1:08:03 PM

  • February 6, 2006 at 4:10 am

    #618918

    Hello,

    Has someone resolve this error ? I have the same message : error: 16954 "Executing SQL directly; no cursor." when I execute a trace of all exceptions.

    I don't find the reason why I have this message. I know that  it's an application with stored procedures who generate this error but I don't find exactly why I have "Executing SQL directly; no cursor".

    Can you help me or explains what means this error ?

    Thank's

    Gaëlle from France.

     

Viewing 6 posts - 1 through 5 (of 5 total)

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