Skip to content

Latest commit

 

History

History
43 lines (30 loc) · 2.18 KB

edit-a-breakpoint-location.md

File metadata and controls

43 lines (30 loc) · 2.18 KB
Raw
title titleSuffix description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords monikerRange
Edit a Breakpoint Location
T-SQL debugger
Learn how to move a breakpoint in a Transact-SQL script file to another location in the script, or to a different script.
markingmyname
maghan
12/04/2019
sql
ssms
conceptual
Transact-SQL debugger, breakpoint location
>=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current

Edit a Breakpoint Location

[!INCLUDE SQL Server]

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.

Editing a Location

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.

To Edit a Breakpoint Location

  1. 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.

  2. 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].

See Also