Navigation:  Advantage SQL > Debugging SQL Script > SQL Debugging Statements >

DEBUG BREAK

Previous pageReturn to chapter overviewNext page

Suspends execution on a specified debuggee or all debuggees.

Syntax

DEBUG BREAK <connection_name | ALL> [NO WAIT]

connection_name ::= identifier

Remark

The DEBUG BREAK statement suspends execution on the specified debuggee or on all debuggees owned by the current debugger. If the debuggee is not executing any SQL script, it will be suspended when attempting to execute the next SQL script.

The debugger session is put into the wait mode (see DEBUB WAIT) unless the NO WAIT clause is specified.

This command is most useful when trying to identify long running or infinite loops in a script. After suspending the execution of a script, the execution stack may be examined to find suspicious loops.

A useful application of the DEBUG BREAK ALL command is found in conjunction with the DEBUG DATABASE command to debug SQL scripts executed by applications for which the source code is not available.

Example

// Suspend execution on a debuggee

DEBUG BREAK "CONN0001xxxx"

See Also

DEBUG BEGIN

DEBUG CONNECTION

DEBUG BREAK POINT

DEBUG RUN

DEBUG WAIT

::DEBUG_CONNECTIONS

::DEBUG_STACK

::DEBUG_BREAKS

::DEBUG_VARIABLES

::DEBUG_SOURCES