SQLTreeoPowered by DatabaseOnline
Release notes

SQLTreeo T-SQL Debugger

Every release of SQLTreeo T-SQL Debugger, newest first. Latest version: 2.1.20.

First public version, correctedv2.1.20previewlatest

· Download

  • Step through stored procedures and functions on SQL Server, with the variables, the table variables and the uncommitted changes in view
  • Change the code while it runs, pause on errors and retry, go back to BEGIN TRAN
  • A 30-day trial with every feature; afterwards a license key for debugging

The first public version of SQLTreeo T-SQL Debugger: a debugger for stored procedures and scalar functions on SQL Server and Azure SQL Database.

Changes in this version

  • Breakpoints keep their line of text: lines added or removed above a breakpoint move it with the code.
  • The query window and the edits in the Variables pane work in the call-stack entry you select, the one the Variables pane shows. The paused procedure is still the default.
  • Works on Azure SQL Database, with Microsoft Entra ID sign-in.

Debugging

  • Pick a procedure or function in the Object Explorer (laid out like SSMS’s) with Debug: a double-click, Enter, the Debug button or the right-click menu. Its code opens, a call for it is written in the Batch tab and the run starts in its database (while the debugger is paused, Debug only opens the code); fill in the parameters and press Start. Step into, over and out, set breakpoints (also with a condition, also in the batch; a breakpoint moves with its line when lines are added above it) and watches that pause when a variable changes or reaches a value.
  • The Variables pane shows the parameters, variables, table variables and @@ROWCOUNT, @@ERROR, @@NESTLEVEL and SCOPE_IDENTITY(), with what changed in red. Click a value to change it; right-click a variable to keep an eye on it in the Watches tab, to pause when it changes, to see a table variable’s rows or to copy its value. Hover over a variable in the code to see its value (text in double quotes, so an empty string and trailing spaces show).
  • While a run goes on, the yellow arrow moves through the code and the variables follow; the Speed box slows a run down so that every statement can be watched. Drag the arrow to another line to continue there, or use Run from here.
  • The query window runs T-SQL on the debugged connection, inside the procedure selected in the call stack (the paused one until you select another): its variables, table variables, #temp tables and the open transaction are all there. The Variables pane and the edits there follow the same selection. Results are shown as SSMS shows them, with the rows affected. The pane folds away to a strip under the code and comes back.
  • Change the code while it runs. Edit the procedure in its tab while paused; Continue applies the change and the run goes on with the new code. Save it to the database when you are ready, or discard it.
  • Errors pause the debugger before anything reacts to them: fix the data or the code and Retry, Skip the statement, go Back to BEGIN TRAN (the transaction is rolled back and the variables are put back), or let the error take its course as SQL Server would.

Connecting

The connection dialog of SQLTreeo Compare: Windows, SQL Server or Microsoft Entra ID authentication, saved connections, Test connection. The database is optional: empty means the login’s default database. On SQL Server the Object Explorer shows every database of the server, with the system databases in their own folder; a run starts in the database of the procedure you picked (the “Runs in” box in the Batch tab shows it), and a procedure in another database opens as db.schema.name and runs in its own database (the debugger switches with USE and back afterwards). Azure SQL Database shows the objects of the database you connect to; the other databases offer “Connect to this database to see its objects”. The last connection opens again at the next start.

Trial and license

The first 30 days are a trial with every feature. After the trial you can still open procedures and functions, read their code and run queries; debugging and saving procedures to the database then need a license key, entered under Settings (the gear next to the connection). Keys are verified online and keep working for 30 days without a connection.

Ideas and feedback

The speech bubbles next to the connection open Ideas and feedback: vote for what we build next, suggest an idea, send us a message or rate the debugger. What is sent goes to the SQLTreeo license service with the version and a random installation id; never any database, code or connection details.

Tested on SQL Server 2025 (LocalDB). The installed version checks for updates by itself; the portable zip and the single exe do not.

First public versionv2.1.19preview

· Download

  • Step through stored procedures and functions on SQL Server, with the variables, the table variables and the uncommitted changes in view
  • Change the code while it runs, pause on errors and retry, go back to BEGIN TRAN
  • A 30-day trial with every feature; afterwards a license key for debugging

The first public version of SQLTreeo T-SQL Debugger: a debugger for stored procedures and scalar functions on SQL Server and Azure SQL Database.

Changes in this version

  • Breakpoints keep their line of text: lines added or removed above a breakpoint move it with the code.
  • The query window and the edits in the Variables pane work in the call-stack entry you select, the one the Variables pane shows. The paused procedure is still the default.
  • Works on Azure SQL Database, with Microsoft Entra ID sign-in.

Debugging

  • Pick a procedure or function in the Object Explorer (laid out like SSMS’s) with Debug: a double-click, Enter, the Debug button or the right-click menu. Its code opens, a call for it is written in the Batch tab and the run starts in its database (while the debugger is paused, Debug only opens the code); fill in the parameters and press Start. Step into, over and out, set breakpoints (also with a condition, also in the batch; a breakpoint moves with its line when lines are added above it) and watches that pause when a variable changes or reaches a value.
  • The Variables pane shows the parameters, variables, table variables and @@ROWCOUNT, @@ERROR, @@NESTLEVEL and SCOPE_IDENTITY(), with what changed in red. Click a value to change it; right-click a variable to keep an eye on it in the Watches tab, to pause when it changes, to see a table variable’s rows or to copy its value. Hover over a variable in the code to see its value (text in double quotes, so an empty string and trailing spaces show).
  • While a run goes on, the yellow arrow moves through the code and the variables follow; the Speed box slows a run down so that every statement can be watched. Drag the arrow to another line to continue there, or use Run from here.
  • The query window runs T-SQL on the debugged connection, inside the procedure selected in the call stack (the paused one until you select another): its variables, table variables, #temp tables and the open transaction are all there. The Variables pane and the edits there follow the same selection. Results are shown as SSMS shows them, with the rows affected. The pane folds away to a strip under the code and comes back.
  • Change the code while it runs. Edit the procedure in its tab while paused; Continue applies the change and the run goes on with the new code. Save it to the database when you are ready, or discard it.
  • Errors pause the debugger before anything reacts to them: fix the data or the code and Retry, Skip the statement, go Back to BEGIN TRAN (the transaction is rolled back and the variables are put back), or let the error take its course as SQL Server would.

Connecting

The connection dialog of SQLTreeo Compare: Windows, SQL Server or Microsoft Entra ID authentication, saved connections, Test connection. The database is optional: empty means the login’s default database. On SQL Server the Object Explorer shows every database of the server, with the system databases in their own folder; a run starts in the database of the procedure you picked (the “Runs in” box in the Batch tab shows it), and a procedure in another database opens as db.schema.name and runs in its own database (the debugger switches with USE and back afterwards). Azure SQL Database shows the objects of the database you connect to; the other databases offer “Connect to this database to see its objects”. The last connection opens again at the next start.

Trial and license

The first 30 days are a trial with every feature. After the trial you can still open procedures and functions, read their code and run queries; debugging and saving procedures to the database then need a license key, entered under Settings (the gear next to the connection). Keys are verified online and keep working for 30 days without a connection.

Ideas and feedback

The speech bubbles next to the connection open Ideas and feedback: vote for what we build next, suggest an idea, send us a message or rate the debugger. What is sent goes to the SQLTreeo license service with the version and a random installation id; never any database, code or connection details.

Tested on SQL Server 2025 (LocalDB). The installed version checks for updates by itself; the portable zip and the single exe do not.