This article is half-done without your Comment! *** Please share your thoughts via Comment ***
SQL Server 2016 enhanced the use of DBCC Commands by adding support of MAXDOP.
A Max Degree of Parallelism (MAXDOP) is used to define some CPU threads at Server Configuration Level as well as at Query Execution Level.
I have read different SQL Forums, and Blogs about the MAXDOP and everyone is saying that the result of MAXDOP is a different basis on your system configuration.
Yes, it is true 100%. Before using MAXDOP you should check your CPU configuration and load of SQL Server.
Once you have defined MAXDOP, you must check the query execution plan and accordingly you should decide the value of MAXDOP.
We are running DBCC CHECKDB for repairing the database related issues. If your database size is huge, it requires more CPU/IO.
Now you can add MAXDOP to optimize the task of DBCC commands.
DBCC with MAXDOP:
1 2 3 4 5 |
DBCC CHECKDB (AdventureWorks2016CTP3) WITH MAXDOP = 2; DBCC CHECKTABLE ('Person.AddressType') WITH MAXDOP = 2; |
Related Article:
Leave a Reply