SQL Server Check

Priority Boost

This is one of many SQL Server checks performed by our free sp_Check tools.

Learn More About Our sp_check Tools

Checks Performed

ID
Check
631
Priority Boost Enabled

What’s the issue?

The priority boost server configuration option controls whether SQL Server runs at a higher Windows scheduling priority than normal applications. When enabled, the SQL Server process is assigned a higher priority class, which causes Windows to schedule its threads ahead of most other processes on the host.

The setting was introduced in much older versions of SQL Server, when hardware constraints made prioritization more relevant, and is disabled by default. It has been deprecated for many years and is documented by Microsoft as a setting that should not be enabled.

This finding identifies instances where priority boost is currently set to 1. The condition is detected by querying sys.configurations for the option and comparing the configured and running values.

Why is this a problem?

Priority Boost drains resources from Windows itself. Elevating SQL Server above the operating system’s own scheduling needs can starve critical system processes, including networking, storage drivers, and the cluster service, producing symptoms that appear unrelated to SQL Server but are caused directly by the setting.

The consequences documented by Microsoft include server instability, network connectivity failures, cluster health check failures and unexpected failovers, and in some cases full system crashes. The failure modes are unpredictable and difficult to diagnose, since the underlying cause is a scheduling priority change rather than any specific SQL Server behavior.

The setting also provides no meaningful benefit on modern hardware. Whatever advantage it may have offered on constrained systems decades ago is not present on current servers, where SQL Server already receives ample CPU scheduling under normal priority. Microsoft’s guidance is unambiguous that the option should be left disabled, and it is marked for removal in a future release.

What should you do about this?

Confirm the current setting with EXEC sp_configure 'priority boost'; and note whether the configured value and the running value match, since a mismatch indicates a pending change awaiting restart.

Disable the setting with EXEC sp_configure 'priority boost', 0; RECONFIGURE; and schedule a SQL Server service restart, since the change requires a restart to take effect. Plan the restart during an appropriate maintenance window and confirm after the restart that both value and value_in_use show 0 in sys.configurations.

Investigate why the setting was enabled to determine whether it reflects a broader pattern of applying outdated tuning advice. Instances configured with Priority Boost often carry other legacy settings that similarly warrant review, so it is worth checking related configuration at the same time.

Type

Reliability

Importance

High

sp_Checks