Can anyone enlighten me as to how the debugger in Query Analyser is supposed to work? I've tried setting breakpoints in the SQL code, as instructed, but execution never stops, and the proc just runs to completion. It's probably something blindingly obvious, but I can't see it!

Cheers,

Chris

There are two secrets to success in this world:
1. Never tell everything you know

__________________
There are two secrets to success in this world:
1. Never tell everything you know

It works for me. (You knew someone would say that, right? ;))

You right click the stored procedure, select debug, then set a breakpoint by clicking on the line and hitting F9 to set (toggle) a breakpoint on the selected line. You then hit F5 (or click GO). Execution stops for me at the line where the breakpoint is set.

When you enter the procedure in debug mode (after entering parameters, if any) by clicking on execute, you will be placed on the first executable line of the procedure, in effect at an invisible breakpoint on that first line.

(You're not setting a breakpoint there are you ? )

Jeff Mason
Custom Apps, Inc.
www.custom-apps.com

Thanks Jeff, now I understand how my users feel :)!
Actually I wonder if there is something not quite right with the setup. As I said, as soon as I hit the execute button from the debug popup, it runs to completion. At that point, I can only hit 'GO' or toggle /clear breakpoints. Step into, over etc are greyed out. Setting breakpoints and hitting go just make the damn thing run to completion again. Perhaps I should try running a broken proc? ;)
Are you aware of any 'undocumented' settings that might be incorrect on the server?

Chris


There are two secrets to success in this world:
1. Never tell everything you know

I found this in BOL:

"The debugger supports traditional functionality such as setting breakpoints, defining watch expressions, and single stepping through procedures. This functionality is available when the SQL Server service uses a domain user account.

In a client/server environment, the client workstation running the debugger must be a member of the same domain as the computer running the corresponding instance of SQL Server."

Are you using the local system account for the instance of SQL Server? Set up a domain account just for SQL Server to use, and use that instead. Change the Log On account in the MSSQLSERVER service properties to use a domain account, not the Local System Account.



Jeff Mason
Custom Apps, Inc.
www.custom-apps.com