A very common question I often receive during Comprehensive Database Performance Health Check is what is the best value for Maximum Worker Threads. Well, I have finally decided to write an answer to this one. In most cases, it is Zero (0). Yes, you heard it correct, zero.
In this SQL in Sixty Seconds Video, we will learn about Best Value for Maximum Worker Threads and why it should kept to be zero most of the time. Additionally, we will also focus on the logic of the default value for the Maximum Worker Threads.
Here is the video.
The script used in this video is as follows:
SELECT cpu_count, max_workers_count FROM sys.dm_os_sys_info
Well, that’s it for today. If you liked this video, please do not forget to subscribe to my YouTube Channel – SQL in Sixty Seconds.
Here are my few recent videos and I would like to know what is your feedback about them.
- Copy Database – SQL in Sixty Seconds #169
- 9 SQL SERVER Performance Tuning Tips – SQL in Sixty Seconds #168
- Excel – Sum vs SubTotal – SQL in Sixty Seconds #167
- 3 Ways to Configure MAXDOP – SQL in Sixty Seconds #166
- Get Memory Details – SQL in Sixty Seconds #165
- Get CPU Details – SQL in Sixty Seconds #164
- Shutdown SQL Server Via T-SQL – SQL in Sixty Seconds #163
- SQL Server on Linux – SQL in Sixty Seconds 162
- Query Ignoring CPU Threads – SQL in Sixty Seconds 161
- Bitwise Puzzle – SQL in Sixty Seconds 160
- Find Expensive Queries – SQL in Sixty Seconds #159
- Case-Sensitive Search – SQL in Sixty Seconds #158
- Wait Stats for Performance – SQL in Sixty Seconds #157
- Multiple Backup Copies Stripped – SQL in Sixty Seconds #156
Reference:Â Pinal Dave (http://blog.SQLAuthority.com)
