You Shall Configure your MAXDOP When Using SharePoint 2013

re: You Shall Configure your MAXDOP When Using SharePoint 2013

Jason — Mon, 11 Mar 2013 20:16:22 GMT

Why don't you raise cost of threshold and use half of your number of processors on DOP? That will work best for many concurrent queries.

re: You Shall Configure your MAXDOP When Using SharePoint 2013

Roger Cormier — Fri, 01 Feb 2013 12:33:32 GMT

Hi SQLSophist,

I can't confirm that the query hints that were used will ever be removed, or that future queries that are written would omit their inclusion. Information regarding why that decision was made is not available to me. What I can confirm is that SharePoint performs a check against the instance every time you try to create a SharePoint database and blocks that type of action if your MAXDOP hasn't been set to 1.

re: You Shall Configure your MAXDOP When Using SharePoint 2013

Gavin Campbell — Fri, 01 Feb 2013 11:42:53 GMT

This is a bit odd. "Historically, Microsoft has been making this recommendation, and adding query hints in order to limit MAXDOP for each query to 1 in order to limit the impact of setting MAXDOP to any value other than 1, or leaving it at 0. This does not appear to be necessary going forward"

If it's indeed the case that query hints are used, not sure why it is necessary to enforce the server setting at all - surely using hints is better from an architecture POV.

Does "this does not appear to be necessary going forward" indicate that the hints are to be removed?

re: You Shall Configure your MAXDOP When Using SharePoint 2013

ValueAddStrategery — Wed, 30 Jan 2013 16:23:45 GMT

sweet synergy!