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?