02 / INTERPRETATION
NUMERASENSE / DBA RESOURCES
FREE TO EXPLORE
SQL Execution Plan Explorer
See how SQL Server operators work together. Inspect realistic sample plans, spot warning signs, and learn what the evidence actually supports.
01 / INVESTIGATION WORKSPACE
Explore a query plan
Choose a scenario, then select any operator in the plan to inspect its role, evidence, and next checks.
Import a real SQL Server execution plan
Drop a .sqlplan file here or choose one from your device. Parsed locally in your browser. No upload.
Drop your .sqlplan here
Execution plan flowSQL Server plans are read right → left
Operator InvestigateNumbers are illustrative, not measured
Example query
03 / PRACTICAL NEXT STEPS
Evidence to collect
Important: Sample plans are illustrative. Imported plans can contain SQL text, object names, and runtime details; files are parsed locally and never sent to NumeraSense. Estimated plans may not include actual runtime metrics. Operator percentages and estimated-versus-actual comparisons do not establish root cause. Validate hypotheses with an actual execution plan, runtime metrics, Query Store, and workload context.
04 / PLAN REGRESSION WORKSPACE
Compare two execution plans
Load Before and After ShowplanXML files to compare structure, operators, row estimates, runtime counters, and explicit warnings. All processing stays in your browser.
Choose two SQL Server .sqlplan files to begin.
Before · operator tree
After · operator tree
Structural and warning differences
Interpretation: Operators are summarized by type, not assumed to be the same operator across plans. Node IDs and estimated costs are not reliable cross-plan identities or runtime measures. Runtime counters may be absent or reflect different executions, parameters, row counts, hardware, or cache states. A changed plan alone does not prove regression.
CONTINUE YOUR INVESTIGATION
From understanding plans to diagnosing SQL Server
Use the Diagnostic Toolkit for read-only investigation scripts, or visit SQL Academy for hands-on DBA training.