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.
Here’s the article for further reading:
Some time ago, I was collecting some Backup & Restore best practices for SharePoint and I came across this post.
It talks about various aspects of backup and restore for a SharePoint farm. Its based on SharePoint 2010 but can be applied to SharePoint 2013.
- IIS Configurations required in a Disaster Recovery
- Backup Scenarios
- Restore Scenarios
- SQL Backup maintenance plans
- Overview of monitoring with SCOM (System Center Operations Manager)
- DPM (System Center Data Protection Manager)
Worth a look: http://blogs.technet.com/b/surama/archive/2012/05/29/sharepoint-2010-backup-and-restore-best-practices.aspx
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. Continue reading