Empty Parallel Zones in SQL Server Execution Plans

Why you can sometimes see two sequential Parallelism operators in SQL Server execution plans.
Why you can sometimes see two sequential Parallelism operators in SQL Server execution plans.
How additional parallel tasks cooperate to complete plan execution, including returning rows to the client.
Exchange synchronization, CXPACKET
waits, and parallel task opening.
Starting the query scan, "early phases" processing, and starting the first parallel tasks.
Iterative execution, invisible plan performance profilers, and how the top-level query scan begins.
The role of the parent task (coordinator) in preparing a plan for parallel execution. Includes initializing each operator and adding hidden profilers to collect runtime performance data such as row count and elapsed time.
An incorrect results bug with batch mode hash joins and a parallel eager table spool used for Halloween Protection. Unfixed before SQL Server 2022.
How SQL Server actual execution plan operator timings work, and why parallel row mode plan timings can be misleading.
Describes the structure of a sql_handle
and explains how the SQL Server batch text hash component is calculated. Provides T-SQL functions to replicate the calculations.
A SQL Server sort operator can replay its results, but only when the sort operates on at most one row. This article employs a sort to avoid a table spool in a query designed to find the closest match to a given value in a second table.
The rare circumstances when a SQL Server sort operator inside a nested loop can rewind (replay) cached results to avoid re-executing child plan operators.
Exploring a new query optimizer exploration rule in SQL Server 2019 can split large batch mode hash aggregates to avoid or reduce spilling to tempdb.
SQL Server has a bug with Halloween Protection when using an OUTPUT
clause on a DELETE
statement.
A MAXDOP n
hint does not limit a SQL Server execution plan to using a maximum of n
CPU cores concurrently 🤯
How and when the SQL Server query optimizer can pull a logical Group By operator above a logical Join.
New instant column data type changes possible in SQL Server 2016 when using data compression.
A few different ways to retrieve distinct values from a table, including some big "it just runs faster" wins in SQL Server 2019.
The SQL Server Eager Index Spool execution plan operator, and the optimizer rules capable of adding it into plans.