| title | Edit a Breakpoint Location | |
|---|---|---|
| titleSuffix | T-SQL debugger | |
| ms.prod | sql | |
| ms.prod_service | sql-tools | |
| ms.technology | scripting | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| ms.assetid | 5c28e411-0377-4210-a7ce-2a5c13dcdf74 | |
| author | markingmyname | |
| ms.author | maghan | |
| ms.reviewer | ||
| ms.custom | seo-lt-2019 | |
| ms.date | 12/04/2019 | |
| monikerRange | >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
The breakpoint location specifies the line and character where the breakpoint resides in a [!INCLUDEtsql] script file. You can edit the breakpoint location to move the breakpoint to another location in the script, or to a different script.
When you edit a breakpoint location, the breakpoint moves to the new location, carrying with it all of the existing properties, such as a hit count or condition.
-
In the editor window, right-click the breakpoint glyph, and then click Location on the shortcut menu.
-or-
In the Breakpoints window, right-click the breakpoint glyph, and then click Location on the shortcut menu.
-
In the File Breakpoint dialog box, edit File to specify a new file, Line to specify a new line, or Character to specify a new location within the line. If the new file you specify is already open in a query editor window, the breakpoint is moved to that editor window. If the file is not opened, a new editor window is opened, the file is loaded in, and the breakpoint moved to the new location.
The Allow the source code to be different from the original version option has no effect when debugging [!INCLUDEtsql].