SQL Server
United States (English) Sign in
Home 2012 2008 R2 2008 Previous Versions Library Forums
TechNet Library
SQL Server
SQL Server 2012
Product Documentation
Books Online for SQL Server 2012
Database Engine
Database Engine Features and Tasks
Database Engine Cross-Instance Features
Administer Servers by Using Policy-Based Management
Monitor and Enforce Best Practices by Using Policy-Based Management
Asymmetric Keys Encryption Strength
Backup Files Must Be on Separate Devices from the Database Files
Check Disk I/O Subsystem for I/O Delay Problems
Check Disk I/O Subsystem for Read Retry Problems
Check Integrity of Database with Suspect Pages
Correct Affinity Mask and Affinity I/O Mask Overlap
Default Trace Log Files Disabled
Detect Failed I/O Request
Detect SCSI Host Adapter Issues
Device Driver Control Error
Device Not Ready Error
Disable Lightweight Pooling
Guest Permissions on User Databases
I/O Error During Hard Page Fault
Increase or Disable Blocked Process Threshold
Keep the Affinity Mask Default Value
Keep the Locks Configuration Option Default Value
Network Packet Size Should Not Exceed 8060 Bytes
Outdated Backup
Place Data and Log Files on Separate Drives
Server public Permissions
Set the AUTO_CLOSE Database Option to OFF
Set the AUTO_SHRINK Database Option to OFF
Set the Collation of User-defined Databases to Match Those of the master and model Databases
Set the Max Degree of Parallelism Option for Optimal Performance
Set the PAGE_VERIFY Database Option to CHECKSUM
SQL Server Login Password Expiration
SQL Server Login Password Strength
Storage System I/O Time-out
Symmetric Keys on System Databases
Symmetric Keys on User Databases
Trustworthy Bit
Unexpected System Failures
Use Database Mail Instead of SQL Mail
Verify Max Worker Threads Setting
Expand Minimize
This topic has not yet been rated - Rate this topic

Verify Max Worker Threads Setting

SQL Server 2012

This rule checks the max worker threads server option for potentially incorrect settings. Setting the max worker threads option to a small value may prevent enough threads from servicing incoming client requests in a timely manner and could lead to "thread starvation". However, setting the option to a large value can waste address space, because each active thread consumes 512 KB on 32-bit servers and up to 4 MB on 64-bit servers.

Set the max worker threads option to 0. This enables SQL Server to automatically determine the correct number of active worker threads based on user requests.

Did you find this helpful?
(1500 characters remaining)

Community Additions

ADD
© 2013 Microsoft. All rights reserved.