Paste the XML of a SQL Server execution plan (.sqlplan) and the parser explains what is actually slow and why. Everything runs locally in your browser — the plan is never uploaded.
CREATE INDEX statements to review.CONVERT_IMPLICIT) that block index seeks or skew cardinality estimates.SET STATISTICS IO, but per operator.DECLARE statements for reproducing the issue..sqlplan file and paste its contents.SELECT qp.query_plan FROM sys.dm_exec_cached_plans cp CROSS APPLY sys.dm_exec_query_plan(cp.plan_handle) qp;query_plan column of sys.query_store_plan.Plans from the cache and Query Store are estimated plans. Actual row counts, reads, spills and waits are only available in an actual plan.
No. The XML is parsed with JavaScript in your browser. Nothing is uploaded or stored, so plans containing table names or parameter values stay on your machine.
Common causes are outdated or missing statistics, parameter sniffing (the plan was compiled for a different parameter value), table variables, local variables, functions in predicates and correlated columns. The parser highlights the operator where the estimate first goes wrong — that is usually where to start.
When a column and the value it is compared to have different data types (for example a varchar column compared to an nvarchar parameter), SQL Server converts one side. If the column side is converted, an index seek may become a scan. Fix it by matching the parameter or literal data type to the column.
A Sort or Hash operator did not get enough memory and wrote data to TempDB, which is much slower than memory. The usual root cause is a row underestimate below that operator, so the memory grant was sized too small.
No. Missing index hints are generated per query, ignore existing similar indexes and do not consider write overhead. Combine overlapping suggestions, check the column order and compare with the existing indexes before creating anything.