These are just a few notes that I have made while doing my new SQL Server 2012 install, ready for SharePoint 2013.
Service Accounts (Server Configuration)
Always make sure that you have all your service accounts created be you start (naming conventions may vary, but this is what I like), also the number of service accounts may vary depend on what features you are installing.
- sql_admin (use this account to login and install SQL)
- sql_agent (SQL Server Agent)
- sql_engine (SQL Server Database Engine)
- sql_analysis (SQL Server Analysis Services)
- sql_reporting (SQL Server Reporting Services)
- sql_integration (SQL Server Integration Services 10.0)
Collation Settings (Server Configuration)
When I got to the “Collation” tab I did some googling and found this Microsoft article (2008668), where it states:
We support any CI collation for the SQL instance (for master, tempdb databases). However we recommend using Latin1_General_CI_AS_KS_WS as the instance default collation (master, tempdb databases).
So I changed my settings to match.
Data Directories (Database Engine Configuration)
I got to the “Data Directories” and I tried to back sense of all the directories (what needs to go where).
I had configured the server to have the following drives:
- E:\ (System Database)
- Q:\ (Backup Database)
- T:\ (Temp Database)
- U:\ (User Database)
- V:\ (User Database Log)
So this is how I did my settings:
Max Degree of Parallelism
Once SQL has finished installing and you have rebooted, open “Microsoft SQL Server Management Studio” and connect to your new SQL instance.
Right click on your server and select “Properties”.
Next, select “Advanced” option on the left pane and change the Max Degree of Parallelism from 0 to 1, click OK.
If you don’t do this change now you may get the following error when performing the Configuration Wizard later.
I hope these few tips will help you with your installation.
There are loads of guides on the web that go into more detail with lots of screenshots to help, here are just a few:
I hope you find this useful.
Disclaimer: I’m no SQL expert and I don’t do may SQL installations (just when a new version of SharePoint is released), I have just written my findings and tips here, so please make sure you do your own research before carrying out any installations.