This is a nice video by Brent Ozar on AlwaysOn Availability Groups: Real-Life Lessons Learned.
In this video, Brent explains what is ‘AlwaysOn’, AlwaysOn Availability Groups and the way that they work. AlwaysOn Failover Clustering is exactly the same as the Failover clustering but AlwaysOn Availability Groups is different – requires SQL 2012 Enterprise.
Brent talks about issues with hotfixes and keeping on top of them and real life Microsoft support issues.
Lessons learned on Windows Setup, Quorum Backups and Monitoring.
Note – this blog post has a title ‘best practices’. I named it so to match the referred TechNet article entitled “Best practices for SQL Server in a SharePoint Server farm”. So please forgive me for using the term ‘best practices’. Probably ‘guidelines’ or ‘good practices’ is a better name for this article.
Getting back to the topic: Some times you need a refresher when it comes to guidelines in setting up SQL for SharePoint – especially when setting up the newer SharePoint 2013.
There is a Technet article I would like to refer to here which specifically refers to ‘best practices’ for SQL server in a SharePoint 2013 environment. There are a few changes to note when it comes to SharePoint 2013.
A couple of important things to note:
Do not enable auto-create statistics on a server that hosts SQL Server and SharePoint Server. Enabling auto-create statistics is not supported for SharePoint Server.
Set the MAXDOP (max degree of parallelism) setting to 1 and nothing else. Setting the max degree of parallelism to any other number can cause a less optimal query plan to be used that will decrease SharePoint Server 2013 performance.
There is also some guidance on setting up the SQL instance for better performance and managing the SharePoint databases.
When installing SharePoint, a good practice is to use SQL Aliases for your installation. To manage and create a SQL Alias via a gui tool, go to start > run > cliconfg and Enter. Then go to the Alias tab.
In this article, we will discuss a few things to have you installing Reporting Services 2008 R2 with SharePoint 2010 in ‘SharePoint Integrated mode’ – not NATIVE mode using a config file for the SQL set up (Reporting Services is a SQL product) and also integrating Reporting Services with SharePoint (the Central Admin stuff).
A good practice is to move IIS off the system drive to another such as D:
Ok, so you tell your Server guys but they miss out on an important step such as updating the registry to the new D:\inetpub… location. You dont check this since you think they know what they are doing and go ahead and install SharePoint and once you are done, you realise that your Central Admin website has been installed and its virtual directory is located on C: – the system drive.
More recently, last year, Microsoft (Bill Baer and Bryan Porter) published a document on SharePoint 2010 database maintenance. Continue reading to get a summary of what is involved in maintaining databases for SharePoint 2010…