| title | Specify a Breakpoint Condition |
|---|---|
| titleSuffix | T-SQL debugger |
| description | Learn how to establish a breakpoint condition to control whether the debugger performs an action when the breakpoint and hit count are reached. |
| author | dzsquared |
| ms.author | drskwier |
| ms.reviewer | randolphwest |
| ms.date | 09/09/2025 |
| ms.service | sql |
| ms.subservice | ssdt |
| ms.topic | how-to |
[!INCLUDE SQL Server]
A breakpoint condition is a [!INCLUDE tsql] expression that the debugger evaluates when the breakpoint is reached. If the condition is satisfied and any specified hit count reached, the debugger either breaks or performs the action specified for the breakpoint.
The expression specified must be a valid Transact-SQL expression that evaluates to a Boolean value. For more information, see Expressions.
If you specify a breakpoint condition with invalid syntax, a warning message appears immediately. If you specify a condition with valid syntax but invalid semantics, a warning message is displayed the first time the breakpoint is hit. In either case, the debugger breaks execution when the invalid breakpoint is hit.
-
In the editor window, right-click the breakpoint glyph, and then select Conditions... on the shortcut menu.
-or-
In the Breakpoints window, right-click the breakpoint glyph, and then select Settings on the shortcut menu.
-
In the Breakpoint Settings dialog box, select the Conditions option and select Conditional Expression from the dropdown list.
-
Enter a valid Boolean expression for the Conditional Expression.
-
Select Is true if you want to break when the expression evaluates to true, or select When changed if you want to break when the value of the expression changes.
[!NOTE]
The debugger doesn't evaluate the Boolean expression until the first time the breakpoint is reached. If you choose When changed, the debugger doesn't consider the first evaluation to be a change, so the debugger doesn't break on the first evaluation.