Juggler on a beach

MAXDOP: not quite what you think

An important change to the MAXDOP documentation was made last week, with a good write up by Pedro Lopes (Twitter), a Program Manager on the SQL Server team at Microsoft. First though, some background on parallelism. How do parallel queries work on SQL Server? SQL Server uses a costing algorithm to decide how “expensive” a
-> Continue reading MAXDOP: not quite what you think

Proposed SQL Server defaults: cost threshold for parallelism

A few months ago I suggested that the following settings should be the default for most SQL Server instances: Set cost threshold for parallelism to 50 Disable lightweight pooling if it is enabled Disable priority boost if it is enabled Set optimize for ad hoc workloads to enabled Set max server memory (MB) to a
-> Continue reading Proposed SQL Server defaults: cost threshold for parallelism

SQL Server logo

Fix SQL Server with one click

Tempting headline, isn’t it? It might even seem like clickbait, but that’s not the intention. The SQL Server default configuration is not recommended for production environments, and yet I have worked on many production environments that have been set up by people who don’t know that the default configurations are not recommended. These same people
-> Continue reading Fix SQL Server with one click