Step through SQL Server stored procedures and functions, with breakpoints, watches and the variables in view.
The debugger paused in dbo.i_ProcessItems: the arrow shows the next statement, the Variables pane the values. The screenshots on this page show sample data.
A stored procedure paused at a breakpoint, then stepped, watched, queried and retried.
Step through a stored procedure one statement at a time, on the same connection the procedure runs on, and see what each statement does to the data.
Step into, over and out of a procedure, the procedures it calls and its scalar functions. A breakpoint stops at the statement you choose, also with a condition such as @ItemId = 4.
Parameters, variables, table variables and @@ROWCOUNT in view, with what changed since the last stop in red. Watches keep the few variables you follow in front of you.
An error can pause the run before anything reacts to it. Fix the data or the code and retry, or go back to BEGIN TRAN and try again.
Pick a procedure or a function in the Object Explorer and press Debug, or use the right-click menu. Its call is written for you, the run starts in its database, and you press Start or step with Into, Over and Out.
While the run goes on, the arrow moves through the code and the variables follow it. A slow speed lets you watch every statement.
Click left of a line, or press F9, in a procedure or in the batch that calls it. A breakpoint on a line without a statement moves to the next statement, and it moves with its line when you add or remove lines above it.
Give a breakpoint a condition in the Breakpoints tab, so it stops only when the condition is true.
With dozens of variables, you want a few in view. Right-click a variable in the Variables pane and choose Add to watches. A changed value is red, and a watch can pause the debugger when its variable changes.
The query window runs T-SQL on the connection the procedure runs on, in the procedure you select in the call stack. Its variables, table variables, temporary tables and the open transaction are all there.
When a statement fails, the run pauses before anything reacts to the error. Fix the data in the query window or the code, then retry the statement, skip it, or let the error take its course as SQL Server would.
A transaction can be taken back to BEGIN TRAN with its variables, so you can try the same run again.
Connect to SQL Server on your own computer, on a server in your network, in a virtual machine or in the cloud, and to Azure SQL Database. Nothing is installed on the server: the debugger reads the procedure and sends each statement over your normal connection. Sign in with Windows or SQL Server authentication, or with Microsoft Entra ID for Azure SQL Database. Tested on SQL Server 2025 and on Azure SQL Database.
Windows 10 or 11, 64-bit. The installer updates itself; a portable zip and a single file run without installing.
The debugger runs the statements on your own connection. Procedures, table data and connection details are not sent to SQLTreeo.
A 30-day trial starts at the first start, with every feature. After it, the debugger stays a viewer until you enter a license key.
A debug session runs your procedures for real, on the connection you chose. Use a test database when you are not sure what a procedure changes; the debugger does not undo changes the procedure has made before you stop it, except a transaction it can roll back.
Thank you for your purchase. Your license key is on its way to the e-mail address you used at checkout. Not there within an hour? Check your spam folder, or write to servicedesk@sqltreeo.com.
Limited offer: buy any 3 different SQLTreeo products in one checkout and take 30% off.Ends November 30, 2026
Choose your 3A license key is for one person, on up to three computers. The key keeps working for 30 days without a connection to the license service.
Download SQLTreeo T-SQL Debugger and start a 30-day trial. Pick a procedure, press Debug, and see what it does, one statement at a time.