dsccommunity / dsccommunity/SqlServerDsc

SqlServerMaxDop: DynamicAlloc MaxDop setting guidelines updated

Open
#1,413 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue help wanted
Dominant language
PowerShell
Stars
385
Forks
224
PR merge metrics
No merged PRs in 30d

Description

Hello,

The guidelines regarding to the maxdop setting has been updated for SQL Server 2016 and over
The calculation when using DynamicAlloc should be reviewed.

Regards.

Configure the max degree of parallelism Server Configuration Option

Starting with SQL Server 2016 (13.x), use the following guidelines when you configure the max_ degree of parallelism server configuration value:

  • Server with single NUMA node | Less than or equal to 8 logical processors | Keep MAXDOP at or below # of logical processors

  • Server with single NUMA node | Greater than 8 logical processors | Keep MAXDOP at 8

  • Server with multiple NUMA nodes | Less than or equal to 16 logical processors per NUMA node | Keep MAXDOP at or below # of logical processors per NUMA node

  • Server with multiple NUMA nodes | Greater than 16 logical processors per NUMA node | Keep MAXDOP at half the number of logical processors per NUMA node with a MAX value of 16_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the DynamicAlloc MAXDOP calculation in the repository and compare its current behavior with the SQL Server 2016+ guidelines in the linked Microsoft documentation. Confirm the NUMA and processor thresholds that need changing; done when the calculation follows those rules and the relevant verification passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, sql
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.