The SQL debugger allows you to find errors in Transact-SQL scripts, stored procedures, triggers, and functions by observing their behavior at runtime. This page gives additional information on the T-SQL debugger provided by dbForge Studio for SQL Server .
You can benefit from the following features:
- Step-by-step execution, call stack browsing, breakpoints and watches
- Familiar debug windows, commands and shortcuts for SSMS users
- Quick step-in for procedures from Database Explorer window
- Debugging integrated into the procedure editor
T-SQL debugger helps to pinpoint source of errors by stepping through code as it executes. You don't need an external debugging tool anymore as it's been integrated into dbForge Studio for SQL Server.
Debug T-SQL code in a comfortable environment
Debug entire object or run step-by-step instruction debugging by using Step Into, Step Out, Step Over, and Run to Cursor commands from the context menu or the Debugging toolbar.
Evaluate variables and parameters declared in routines with the help of the Watches window.
View the active stack of stored routine calls in the Call Stack window.
Set a Breakpoint to stop execution at any T-SQL code line, manage the list of breakpoints in a separate window.
Familiar user interface
If you are used to the SSMS debugger user interface, you can easily run debugger in Studio for SQL Server — it employs similar debug windows, commands and keyboard shortcuts , so you won't get confused.
Start debugging instantly
When you need to debug a stored procedure, you only have to locate it in the database explorer — Step-in command is available from the context menu. Optionally, start debugging from a stored routine source window, or from the Code toolbar.
Similarly, you can start debugging stored procedures in the procedure editor without switching to additional windows or tabs.