Post reply

T-SQL Debugger for Stored Procs in SQL2K

  • October 18, 2002 at 2:10 pm

    #79240

    Hi,

    I have used the debugger a few times. I found that with a new install of SQL Server 2K, the debugger executes stored procedures,

    but does not allow me to set any break points, or step through the code. The code runs from start to finish.

    I assume this is a configuration setting on the server beacuse I cannot get the debuger to work from 2 workstations, or on the server itself.

    Thanks for your help.

    - John

  • October 20, 2002 at 10:18 am

    #438949

    Haven't had issues myself. If I get the debugger running, usually rights for the service account, I can easily stop at any breakpoint I want.

    Steve Jones

    sjones@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/sjones

  • October 21, 2002 at 5:05 am

    #438985

    It always seems to be accounts. You have to be logged on as user account that as permissions to create the debugger on the server, the sql server needs to be configured with a domain user. And the dcom settings on the sql server need to allow your user account to create the debugger.

    I think that should do it.

    Simon Sabin

    Co-author of SQL Server 2000 XML Distilled

    http://www.amazon.co.uk/exec/obidos/ASIN/1904347088


    Simon Sabin
    SQL Server MVP

    http://sqlblogcasts.com/blogs/simons

  • October 22, 2002 at 7:57 am

    #439122

    Thanks for the help guys.

    I looked in the event viewer and saw errors being raised by an app named SQL Debugging 98. The error said: "SQL Server when started as a service must not log on as a System Account. Reset login as account user using the control panel."

    The problem is that the debugger cannot run unless it is in the security context of a Windows user, just like Simon Sabin said.

Viewing 4 posts - 1 through 4 (of 4 total)

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