So you were quick to jump on SharePoint 2013 Preview, eh? If you are a good SharePoint person and are attempting to run SharePoint Products Configuration Wizard with least privilege, then you are probably at this post because you hit this:
Failed to create the configuration database.
This SQL Service instance does not have the required “maxdegree of parallelism” setting of 1. Database provisioning operations will continue to fail if “maxdgree of parallelism” is not set 1 or the current account does not have permissions to change the setting…
The default setting for this in SQL is 0 and this was not a requirement, but a recommendation, in SharePoint 2010. Our new buddy SharePoint 2013 requires that MAXDOP be set to exactly 1. Furthermore, as foreshadowed above, if you ran the wizard with a highly privilege account on SQL, then the account would automatically make the settings change and continue without this failure. However, for me and many others this is probably not the case.
Don’t get ahead of yourself though and simply make the settings change and re-run the wizard; you’re not out of the woods yet. When this failure occurred, it had already created the SharePoint_Config DB, meaning if you run the wizard again after making the settings change it will fail because the database already exists with the same name. While in SQL Server Management Studio switching MAXDOP make sure to delete the database before re-running the wizard.
Steps to Change Max Degree of Parallelism
Right click on the SQL Service Instance and select Properties
Under Advanced, locate Max Degree of Parallelism under the Parallelism section and switch the settings from 0 to 1.
Click Ok and you can now continue on with your SharePoint 2013 deployment!