Breakpoints specify that the Transact-SQL debugger pause execution on a specific Transact-SQL statement, you can then view the state of the code elements at that point.
When running the Transact-SQL debugger, you can toggle a breakpoint on specific statements. When execution reaches a statement with a breakpoint, the debugger pauses execution so you can view debugging information, such as the values present in variables and parameters.
You can manage breakpoints individually in the editor window, or collectively by using the Breakpoints window. You can edit breakpoints to specify items such as specific conditions under which execution should pause, or the actions to be taken if the breakpoint is executed.
|Describes how to specify the Transact-SQL statement on which you want the debugger to pause.||Toggle a Breakpoint|
|Describes how to temporarily deactivate a breakpoint, and later reactivate it. Also describes how to delete a breakpoint.||Enable, Disable, and Delete Breakpoints|
|Describes how to specify a condition, which defines whether breakpoint breaks based on the evaluation of a specified Transact-SQL expression.||Specify a Breakpoint Condition|
|Describes how to specify a hit count, which causes a breakpoint to break only when the statement containing the breakpoint has been executed a specified number of times.||Specify a Hit Count|
|Describes how to specify a filter, which causes a breakpoint to break for only specified processes or threads.||Specify a Breakpoint Filter|
|Describes how to specify a When Hit action, which is a custom operation that is performed when the breakpoint statement is executed. An example would be to print a message.||Specify a Breakpoint Action|
|Describes how to edit the location of a breakpoint.||Edit a Breakpoint Location|