Skip to content

Latest commit

 

History

History
62 lines (42 loc) · 3.85 KB

step-through-transact-sql-code.md

File metadata and controls

62 lines (42 loc) · 3.85 KB
Raw
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords monikerRange
Step Through Transact-SQL Code
Learn how to use the Transact-SQL debugger to control which Transact-SQL statements are run in a Database Engine Query Editor window.
markingmyname
maghan
03/14/2017
sql
ssms
conceptual
Transact-SQL debugger, debugging code
Transact-SQL debugger, step over
Transact-SQL debugger, step out
Transact-SQL debugger, step into
>=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current

Step Through Transact-SQL Code

[!INCLUDE SQL Server]

The [!INCLUDEtsql] debugger enables you to control which [!INCLUDEtsql] statements are run in a [!INCLUDEssDE] Query Editor window. You can pause the debugger on individual statements and then view the state of the code elements at that point.

[!INCLUDEssms-old-versions]

Breakpoints

A breakpoint signals the debugger to pause execution on a specific [!INCLUDEtsql] statement. For more information about breakpoints, see Transact-SQL Breakpoints.

Controlling Statement Execution

In the [!INCLUDEtsql] debugger, you can specify the following options for executing from the current statement in [!INCLUDEtsql] code:

  • Run to the next breakpoint.

  • Step into the next statement.

    If the next statement invokes a [!INCLUDEtsql] stored procedure, function, or trigger, the debugger displays a new Query Editor window that contains the code of the module. The window is in debug mode, and execution pauses on the first statement in the module. You can then move through the module code, for example, by setting breakpoints or stepping through the code.

  • Step over the next statement.

    The next statement is executed. However, if the statement invokes a stored procedure, function, or trigger, the module code runs until it finishes, and the results are returned to the calling code. If you are sure there are no errors in a stored procedure, you can step over it. Execution pauses on the statement that follows the call to the stored procedure, function, or trigger.

  • Step out of a stored procedure, function, or trigger.

    Execution pauses on the statement that follows the call to the stored procedure, function, or trigger.

  • Run from the current location to the current location of the pointer, and ignore all breakpoints.

The following table lists the various ways in which you can control how statements execute in the [!INCLUDEtsql] debugger.

Action Perform action:
Run all statements from the current statement to the next breakpoint Click Continue on the Debug menu.

Click the Continue button on the Debug toolbar.
Step into the next statement or module Click Step Into on the Debug menu.

Click the Step Into button on the Debug toolbar.

Press F11.
Step over the next statement or module Click Step Over on the Debug menu.

Click the Step Over button on the Debug toolbar.

Press F10.
Step out of a module Click Step Out on the Debug menu.

Click the Step Out button on the Debug toolbar.

Press SHIFT+F11.
Run to the current cursor location Right-click in the Query Editor window, and then click Run To Cursor.

Press CTRL+F10.

See Also