I have the following problem:
When trying to debug a stored procedure with query analyzer it does not
stop at the first line of code. Instead it runs throug the whole
procedure and I cannot stop it! Am I missing something?
Without being able to interrupt the procedure I want to debug, the
debugger is useless...
Regards
Stephan

Did you set breakpoints?
Is there more happening than just one query?

Show quoteHide quote

Stephan Zaubzer (stephan.zaub***@schendl.at) writes:
Getting the debugger to work requires so much red tape that I have
essentially given up on it. The only exception is possibly if QA and
SQL Server is on the same machine.

First check in Help->About in Query Analyzer which version of QA you have.
Then compare that with @@version. If QA has less than 8.00.760 and
@@version is 8.00.760, you need to upgrade your client tools to SP3.

If you are running Windows XP SP2, with or without firewall enabled,
you need SP4 on both server and client, and configure your firewall
to permit the server to connect to you. (But I don't think you have
this problem, as you usually get an error message as I recall.)

Also, the service account under which SQL Server runs needs some
rights on your machine.

There is a section "Troubleshooting the Transact-SQL Debugger" on
Books Online that may give further tips.

On Wed, 23 Aug 2006 16:21:56 +0200, Stephan Zaubzer
<stephan.zaub***@schendl.at> wrote:

There's always the old-school approach of adding temporary PRINTs
into the procedure, provided that you remember to take them out
afterward (or key them to some central flag, e.g. "if table X
contains record Y").

SQL Server 2005 Management Studio vs. 2000 Enterprise Manager/Query Analyzer
SIMPLE command to convert string to number? Not CAST or CONVERT.
Modifying Data Directly through Studio Manager
Cannot edit table data using Enterprise Manager
Maintenance plans not installed