March 9, 2015 at 12:32 pm
We encountered an issue where MAXDOP (Max Degree of Parallelism) may have reverted from 8 to default value of 0, after SQL server 2012 was updated to SP2, CU3.
The logs do not go back far enough to determine if MAXDOP was changed prior to the update or during the update. Does anyone know if any SQL update can change MAXDOP? I did not find anything by searching.
Thanks,
Chad
To restate, the question is, Can a SQL update revert MAXDOP to default?
March 9, 2015 at 1:35 pm
The maxdop setting is relavant to the number of processors
8 or less processors ===> 0 to N (where N= no. of processors)
More than 8 processors ===> 8
NUMA configured ===> MAXDOP should not exceed no of CPU’s assigned to each
NUMA node with max value capped to 8
Hyper threading Enabled ===> Should not exceed the number of physical processors.
Please go through this link hope this may help you.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply