Every release, reconstructed from the project's commit history — what changed, and why.
Plan Visualizer overview line (Seriell/Compile-Zeit-Schätzung), critical/warning detail-panel labels, Parallel: ja/nein, and a handful of code comments missed by the 1.1.1 sweep.
Rule findings/descriptions, query-plan diagnostics, UI status/dialog text, and the HTML/Markdown/baseline-diff report exporters were mixed German while the rest of the codebase, README, and GitHub metadata are English. Content-only change, no logic touched.
QP011 flags statements whose average CPU time or response time per execution clears a threshold (CPU 100ms/1s, elapsed 500ms/5s → Warning/Critical), and derives whether a query is CPU-bound or predominantly waiting — without claiming what it waited on, since no wait DMVs are read anywhere in the project. QP010 now also reports physical reads and logical writes per execution. Both come from the same sys.dm_exec_query_stats row the plan-cache pass already reads, at no extra query cost. Verified end-to-end against SQL Server 2022 with a CPU-burner test procedure.
AP015 flags CASE...END wrapping a column on the left of a predicate comparison (non-SARGable); AP016 flags the col = @p OR @p IS NULL catch-all pattern (a plan-caching/parameter-sniffing issue, not a sargability one). QP010 flags any cached plan containing a table/index scan whose average logical reads per execution clears a noise threshold. Verified with 15 synthetic test cases (zero regressions on the existing 14 rules) and end-to-end against a real scan-forcing test procedure.
AP013 flags LIKE '%...' patterns (forces a scan); AP014 flags arithmetic/concatenation on a column on the predicate's left side. Fixed a real bug surfaced while testing AP014: the WHERE/ON predicate-zone scan (shared by AP004/AP010/AP014) didn't stop at statement boundaries, letting a predicate bleed into the next statement and pick up an unrelated comparison operator.
Plan reading now falls back to Query Store when a plan has been evicted from cache. Database/folder scans run asynchronously with progress and cancel. Plan Visualizer can save/open .sqlplan files directly. New rules: AP009 (UPDATE/DELETE without WHERE, Critical), AP010 (non-SARGable function on a predicate column), AP011 (NOT IN with subquery — NULL trap), AP012 (SELECT TOP without ORDER BY). Baseline save/compare added (JSON), plus a GitHub Actions release workflow.
Native C#/WinForms tool replacing the PowerShell sqmRefactorTool wizard: 10 token-stream anti-pattern/formatting rules, DMV-based query-plan analysis (warnings, unused/duplicate/disabled indexes, DOP/memory-grant overview, top expensive operators, cardinality mismatch, join/parallelism-skew heuristics, missing-index suggestions with generated CREATE INDEX), a graphical execution plan tree with cost heat-map and decisive-problem highlighting, a severity/impact-ranked Problem-Queries view, and HTML/Markdown reports.