0

It's a requirement to install SharePoint 2016 with a SQL Server that has MAXDOP=1. It's long been a best practice to configure SharePoint with its own SQL instance, and this is certainly one reason why. However, SQL 2016 can now set MAXDOP at the database level via Database Scoped Configuration.

Is it possible to install/configure SharePoint 2016 on an instance where MAXDOP!=1, but with MAXDOP=1 at the database level? (perhaps switch maxdop to 1, install SP, and then change maxdop to 0 at the instance level and 1 at the database level for SP databases?)

Improve this question

1 Answer 1

Reset to default
2

SharePoint will still require the instance level configuration of MAXDOP = 1 and will even set it at the instance level during the install process if you have the sysadmin role.

Improve this answer
3
  • I think it only requires it when new databases are created? If so, MAXDOP could be set to 1 for the initial install and then it could be configured at the database level for operational purposes. Is this a clever workaround or am I in bad idea territory? Commented Jul 11, 2017 at 16:05
  • It's not mentioned in official documentation. You can open up a PSS case to see if Microsoft will support it, but as of now, it's unsupported. Commented Jul 11, 2017 at 16:26
  • Confirmed with the PG, it is unsupported. Commented Jul 12, 2017 at 0:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.