Changelog

0.4.0, 7 November 2026

SpDev Pro, with a 14-day free trial.

Profile SQL File measures every statement: time, CPU, logical and physical reads, writes, rows and executions, from SQL Server’s own counters for the session, corrected for the profiler’s own cost. Lines are tinted by cost, with the cost at the end of the line and a detailed hover.
Plan findings from the actual execution plans, shown as problems on their lines with quick fixes: missing indexes (with CREATE INDEX), scans that keep few rows, implicit conversions, parameter sniffing, bad estimates and table variables, key lookups, non-sargable predicates, spills, memory grants, scalar functions and missing join predicates. Also row-by-row loops and cursors, long transactions, and waits.
Profile report: findings, statements, calls, plans, comparison with earlier runs, and Markdown export.
Benchmark SQL File: repeated runs with the median, p95 and spread of every statement.
Sandbox: debug, run or profile inside a transaction that is rolled back.
Coverage: statement and branch coverage of procedures in VS Code’s Test Coverage view.
A Profile CodeLens next to Debug and Run.
The extension is now bundled: it starts faster and downloads less.

Renamed to “SpDev - SQL Procedure Development” on the Marketplace. No code changes.

Rebuilt from the ground up.

Step through procedures and scripts with breakpoints, step over, into and out, step back and reverse continue.
Variables and parameters at every statement, including table variables, table-valued parameters, xml, binary and CLR types.
A call stack across nested and recursive procedures that have local .sql files.
Result sets, PRINT output and SQL Server errors, mapped to the lines of your file. The debugger stops on errors nothing catches.
Attach to Application: debug the procedures a running .NET app calls through EF Core, Dapper or ADO.NET (SpDev.Runtime NuGet package).
Calls written without EXEC (dbo.Proc @Id = @p0) are recognised.
Stepping over the last statement stops once more on END, so you can check the final values and result set.
Parameter prompts based on the procedure’s declared parameters, remembered per file.
Connection strings are kept in VS Code’s secret storage.
Inline variable values while stopped, and hover over @variables.
Hover over *, SELECT or a column name of a statement that has run to see its rows.
Procedures now run as temporary copies instead of running the file’s CREATE PROCEDURE.