Debugger overview
The dbForge Studio debugger is a powerful tool that allows you to observe the run-time behavior of your database object and locate logic errors. With the debugger, you can break, or suspend, execution of your program to examine your database object, evaluate and edit variables in your script.
The dbForge Studio debugger provides the Debug menu with access to debugger tools. Debugger windows and dialog boxes display information about your database object and enable you to enter additional information. You can call Help on any window or a dialog box by pressing F1.
The dbForge Studio debugger provides powerful commands for controlling the execution of your code. Here is the list of the tasks you can perform to control execution using debugger commands:
- Starting (or continuing) execution of procedures, functions, triggers, and SQL scripts
- Breaking execution of procedures, functions, triggers, and SQL scripts
- Stopping execution of procedures, functions, triggers, and SQL scripts
- Stepping through the procedures, functions, triggers, and SQL scripts
- Running to a specified location
- Setting the execution point
Requirements for starting the Debugger
When you attempt to start the Debugger, the following requirements should be fulfilled:
- Server-side and client-side components of T-SQL Debugger must be installed
- Debugging Firewall exceptions on the client and server sides must be enabled
- The Database Engine SQL document must be connected using the Windows Authentication or SQL Server Authentication under the login that is a member of the sysadmin fixed server role
- The Database Engine SQL document must be connected to a Database Engine instance of SQL Server 2005 SP2 or later. You cannot run the Debugger when the SQL document is connected to an instance that is in the single-user mode
Note:
The Debugger does not work with the Azure SQL Database.
For more information about how to configure the Debugger, see Transact-SQL Debugger.
Debug layout
dbForge Studio has two window layouts - default layout and debug layout. Debug layout is applied when you start debugging, the rest of the time you work in the default layout. Both layouts preserve their state when starting/stopping debugging or exiting from dbForge Studio. The Watches and Call Stack windows are available only in debug layout.
Additionally, you can read how to debug a stored procedure in the How to Debug a Stored Procedure with dbForge Studio for SQL Server post.
Want to Find out More?
Overview
All features
Request a demo
