New releases of SQL Server always have an impact on SharePoint. SharePoint depends so heavily on the functionality provided by SQL Server that there is usually a SharePoint Service Pack released to enable full supported compatibility.
This post focuses on compatibility issues with SharePoint 2013, not with SharePoint 2010.
SQL Server Enhancements
A lot of enhancements have been made to the database engine. Although SharePoint will not allow some of these features to be configured or utilised, some of them are available for utilisation.
Not applicable to SharePoint
Memory-Optimized Tables – This feature allows for vastly improved performance under specific circumstances.
Applicable to SharePoint
Azure Data Files – SQL Server 2014 will support the use of Azure storage as locations for database files.
Azure Hosted Installation – A wizard is available to install SQL Server 2014 on an Azure VM.
Backup Encryption – The database backups can now be encrypted.
Always-On Availability Groups – Multiple improvements have been made to allow management of AOAG, along with additional support for Azure.
Database Compatibility Level – Level 90 (SQL Server 2005) is no longer supported.
SQL Server 2014 Reporting Services is unchanged from the previous version.
SQL Server 2014 Analysis Services is pretty much unchanged from the previous version. Improvements to development tools are covered under this component.
There is now a Visual Studio 2012 SQL Server Data Tools version that includes Business Intelligence templates – More info
SQL Server 2014 Integration Services is unchanged from the previous version.
SharePoint 2013 will support SQL Server 2014 following installation of SharePoint 2013 SP1 AND SharePoint 2013 April 2014 CU.
Following the release of SP1 an issue was found that prevented the installation of further SPs and CUs and so SP1 has been withdrawn. The April 2014 CU has not been built from the component hotfixes yet.
This means that currently there is no SharePoint 2013 support for SQL Server 2014.
At present it is unclear whether SharePoint 2010 will ever fully support SQL Server 2014.
The SQL Server 2012 Reporting Services Native Mode report server cannot run side-by-side with SQL Server 2014 Reporting Services SharePoint Components
The Reporting Services Native mode Windows service ‘SQL Server Reporting Services’ (ReportingServicesService.exe) fails to start if there are SQL Server 2014 Reporting Services SharePoint components installed on the same server.
Uninstall SQL Server 2014 Reporting Services SharePoint components and restart Microsoft SQL Server 2012 Reporting Services Windows service.
Required Upgrade Order for Multi-node SharePoint Farm to SQL Server 2014 Reporting Services
Report rendering in a multi-node farm fails if instances of the Reporting Services SharePoint Shared Service are upgraded before all instances of the Reporting Services Add-in for SharePoint Products.
In a multi-node SharePoint farm:
- First upgrade all instances of the Reporting Services Add-in for SharePoint Products.
- Then upgrade all instances of the Reporting Services SharePoint Shared Service.
MSOLAP.5 must be downloaded, installed and registered for a SharePoint 2013 new farm configured with SQL Server 2014
For a SharePoint 2013 farm configured with a SQL Server 2014 deployment, Excel workbooks referencing the MSOLAP.5 provider cannot connect to tabula data models because the provider referenced in the connection string is not installed.
Download the MSOLAP.5 provider from the SQL Server 2012 SP1 Feature Pack. Install the provider on the application servers running Excel Services. For more information, see the section “Microsoft Analysis Services OLE DB Provider for Microsoft SQL Server 2012 SP1” Microsoft SQL Server 2012 SP1 Feature Pack.
Register MSOLAP.5 as a trusted provider with SharePoint Excel Services. For more information, see Add MSOLAP.5 as a Trusted Data Provider in Excel Services.