Updates from: 02/24/2022 02:21:59
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Overview Of Sql Server In A Sharepoint Server 2013 Environment https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/overview-of-sql-server-in-a-sharepoint-server-2013-environment.md
SQL Server 2008 R2 introduced Power Pivot for SharePoint and Power Pivot for Exc
### SQL Server Reporting Services in SharePoint Integrated Mode <a name="RSint"> </a>
-SQL Server 2008 R2 Reporting Services supports two types of SharePoint integration. Full integration relies on the SharePoint integrated mode. Partial integration relies on two Web Parts, Report Explorer and Report Viewer, which you must install on a SharePoint site and point to a remote report server instance. For more information, see [Overview of Reporting Services and SharePoint Technology Integration](/previous-versions/sql/sql-server-2008-r2/bb326358(v=sql.105)) and [Planning for SharePoint Integration](/previous-versions/sql/sql-server-2008-r2/bb326405(v=sql.105)).
+SQL Server 2008 R2 Reporting Services supports two types of SharePoint integration. Full integration relies on the SharePoint integrated mode. Partial integration relies on two Web Parts, Report Explorer and Report Viewer, which you must install on a SharePoint site and point to a remote report server instance. For more information, see [Overview of Reporting Services and SharePoint Technology Integration](/previous-versions/sql/sql-server-2008-r2/bb326358(v=sql.105)&preserve-view=true) and [Planning for SharePoint Integration](/previous-versions/sql/sql-server-2008-r2/bb326405(v=sql.105)&preserve-view=true).
> [!NOTE] > Reporting Services supports SharePoint integrated mode using SharePoint Server 2013 only.
We recommend AlwaysOn Availability Groups for high availability in SQL Server 20
> [!NOTE] > We recommend that you use AlwaysOn Availability Groups instead of database mirroring for your high availability solution with SQL Server 2012 or SQL Server 2014 and SharePoint Server 2013. For more information, see [Overview of SQL Server High-Availability Solutions](/sql/database-engine/sql-server-business-continuity-dr).
-For more information, see [AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server), and [Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-2017).
+For more information, see [AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server), and [Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-2017&preserve-view=true).
### Reporting Services SharePoint mode <a name="RSsp"> </a>
-SharePoint mode in SQL Server 2012 Reporting Services and SQL Server 2014 Reporting Services is a SharePoint Server 2013 shared service that you configure in either the SharePoint Central Administration website or by using Reporting Services SharePoint mode Microsoft PowerShell cmdlets. For more information, see [PowerShell cmdlets (Reporting Services SharePoint Mode)](/sql/reporting-services/report-server-sharepoint/powershell-cmdlets-for-reporting-services-sharepoint-mode?view=sql-server-2016). SharePoint mode supports SharePoint Server 2013 backup and restore for SQL Server Reporting Services service application and Unified Logging Service (ULS) trace logs. SharePoint mode also supports claims-based authentication. For more information, see the "SharePoint Mode" section of [What's New (Reporting Services)](/previous-versions/sql/sql-server-2012/ms170438(v=sql.110)). For more information about the SharePoint Microsoft PowerShell cmdlets for ULS, see [Logging and events cmdlets in SharePoint 2013](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true).
+SharePoint mode in SQL Server 2012 Reporting Services and SQL Server 2014 Reporting Services is a SharePoint Server 2013 shared service that you configure in either the SharePoint Central Administration website or by using Reporting Services SharePoint mode Microsoft PowerShell cmdlets. For more information, see [PowerShell cmdlets (Reporting Services SharePoint Mode)](/sql/reporting-services/report-server-sharepoint/powershell-cmdlets-for-reporting-services-sharepoint-mode?view=sql-server-2016&preserve-view=true). SharePoint mode supports SharePoint Server 2013 backup and restore for SQL Server Reporting Services service application and Unified Logging Service (ULS) trace logs. SharePoint mode also supports claims-based authentication. For more information, see the "SharePoint Mode" section of [What's New (Reporting Services)](/previous-versions/sql/sql-server-2012/ms170438(v=sql.110)). For more information about the SharePoint Microsoft PowerShell cmdlets for ULS, see [Logging and events cmdlets in SharePoint 2013](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true).
SharePoint mode requires that a report server component of Reporting Services must run within a SharePoint Server farm. This means that a SharePoint application server must exist with the Reporting Services shared service installed and at least one Reporting Services service application.
-For more information, see [Reporting Services Report Server (SSRS)](/sql/reporting-services/report-server-sharepoint/reporting-services-report-server) and [Reporting Services Report Server (SharePoint Mode)](/sql/reporting-services/report-server-sharepoint/reporting-services-report-server-sharepoint-mode?view=sql-server-2016).
+For more information, see [Reporting Services Report Server (SSRS)](/sql/reporting-services/report-server-sharepoint/reporting-services-report-server) and [Reporting Services Report Server (SharePoint Mode)](/sql/reporting-services/report-server-sharepoint/reporting-services-report-server-sharepoint-mode?view=sql-server-2016&preserve-view=true).
### Business intelligence features <a name="BI"> </a>
When you install SQL Server 2012 Analysis Services (SSAS) and SQL Server 2012 Re
The xVelocity in-memory analytics engine in SQL Server 2012 supports both self-service BI and corporate BI. For more information, see [xVelocity in SQL Server 2012](/previous-versions/sql/sql-server-2012/hh922900(v=sql.110)). +
+For more information, see [Guidance for Using SQL Server BI Features in a SharePoint Farm](https://technet.microsoft.com/library/hh231680.aspx), [Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1)](/sql/sql-server/install/guidance-for-using-sql-server-bi-features-in-a-sharepoint-2010-farm?view=sql-server-2014&preserve-view=true), and [Install SQL Server BI Features with SharePoint (PowerPivot and Reporting Services)](/previous-versions/sql/sql-server-2016/hh231671(v=sql.130)).
+ For more information, see [Install SQL Server BI Features with SharePoint (PowerPivot and Reporting Services)](/previous-versions/sql/sql-server-2016/hh231671(v=sql.130)).+ ### Power Pivot for SharePoint 2013 <a name="PP"> </a>
-SQL Server 2012 with SP1 is required to deploy Power Pivot for SharePoint 2013. Power Pivot for SharePoint 2013 is a SharePoint Server service application that becomes available when Analysis Services runs in SharePoint mode. This provides a server that hosts Power Pivot data in a SharePoint farm. SQL Server 2012 Analysis Services provides three modes for analysis, Multidimensional, Tabular, and Power Pivot for SharePoint. Note that each server mode is independent of the others, and each supports a type of analytical database that only runs in that modality. For more information about SQL Server 2012 Analysis Services (SSAS), see [Analysis Services](/previous-versions/sql/sql-server-2012/bb522607(v=sql.110)). For more information about SQL Server 2014 Analysis Services, see [Analysis Services](/sql/analysis-services/analysis-services?view=sql-server-2014). The server that hosts Power Pivot for SharePoint 2013 can be outside a SharePoint Server 2013 farm.
+SQL Server 2012 with SP1 is required to deploy Power Pivot for SharePoint 2013. Power Pivot for SharePoint 2013 is a SharePoint Server service application that becomes available when Analysis Services runs in SharePoint mode. This provides a server that hosts Power Pivot data in a SharePoint farm. SQL Server 2012 Analysis Services provides three modes for analysis, Multidimensional, Tabular, and Power Pivot for SharePoint. Note that each server mode is independent of the others, and each supports a type of analytical database that only runs in that modality. For more information about SQL Server 2012 Analysis Services (SSAS), see [Analysis Services](/previous-versions/sql/sql-server-2012/bb522607(v=sql.110)). For more information about SQL Server 2014 Analysis Services, see [Analysis Services](/sql/analysis-services/analysis-services?view=sql-server-2014&preserve-view=true). The server that hosts Power Pivot for SharePoint 2013 can be outside a SharePoint Server 2013 farm.
To configure Power Pivot for SharePoint you can use the SharePoint Central Administration website, the Power Pivot for SharePoint 2013 Configuration tool, or Microsoft PowerShell cmdlets. The following table lists each method and describes the process:
To configure Power Pivot for SharePoint you can use the SharePoint Central Admin
|Power Pivot for SharePoint 2013 Configuration Tool <br/> |Evaluates an existing installation and determines what needs to be configured in the SharePoint farm and Power Pivot for SharePoint and then configures everything required. <br/> | |Microsoft PowerShell cmdlets <br/> |Provides cmdlets that you can use to build PowerShell script files (.ps1) and automate the configuration process for Power Pivot for SharePoint. <br/> |
-The Power Pivot for SharePoint 2013 add-in enables PowerPivot Gallery, Schedule Data Refresh, and the PowerPivot Management Dashboard in Central Administration. For more information, see [PowerPivot for SharePoint (SSAS)](/sql/analysis-services/power-pivot-sharepoint/power-pivot-for-sharepoint-ssas?view=sql-server-2017).
+The Power Pivot for SharePoint 2013 add-in enables PowerPivot Gallery, Schedule Data Refresh, and the PowerPivot Management Dashboard in Central Administration. For more information, see [PowerPivot for SharePoint (SSAS)](/sql/analysis-services/power-pivot-sharepoint/power-pivot-for-sharepoint-ssas?view=sql-server-2017&preserve-view=true).
## See also <a name="sec4"> </a>
The Power Pivot for SharePoint 2013 add-in enables PowerPivot Gallery, Schedule
[Supported Combinations of SharePoint and Reporting Services Components](/sql/reporting-services/install-windows/supported-combinations-of-sharepoint-and-reporting-services-server?viewFallbackFrom=sql-server-2014)
-[What's New (Analysis Services)](/sql/analysis-services/what-s-new-in-analysis-services?view=sql-server-2017)
+[What's New (Analysis Services)](/sql/analysis-services/what-s-new-in-analysis-services?view=sql-server-2017&preserve-view=true)
[Features Supported by the Editions of SQL Server 2014](/sql/sql-server/editions-and-components-of-sql-server-2016)
SharePoint Overview Of Sql Server In Sharepoint Server 2016 And 2019 Environments https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/overview-of-sql-server-in-sharepoint-server-2016-and-2019-environments.md
description: "Learn about the SharePoint Server relationship with SQL Server and
# Overview of SQL Server in SharePoint Server 2016 and 2019 environments The minimum requirements for a database server in SharePoint Servers 2016 and 2019 are as follows:
SharePoint Server 2019 supports the following:
- SQL Server 2016 Analysis Services (SSAS) > [!NOTE]
-> SQL Server Reporting Services integration with SharePoint Server 2019 is no longer supported. For more information, see [Reporting Services Report Server (SharePoint Mode)](/sql/reporting-services/report-server-sharepoint/reporting-services-report-server-sharepoint-mode?view=sql-server-2016&viewFallbackFrom=sql-server-2017) and [Supported combinations of SharePoint and Reporting Services server](/sql/reporting-services/install-windows/supported-combinations-of-sharepoint-and-reporting-services-server?view=sql-server-2016).
+> SQL Server Reporting Services integration with SharePoint Server 2019 is no longer supported. For more information, see [Reporting Services Report Server (SharePoint Mode)](/sql/reporting-services/report-server-sharepoint/reporting-services-report-server-sharepoint-mode?view=sql-server-2016&viewFallbackFrom=sql-server-2017&preserve-view=true) and [Supported combinations of SharePoint and Reporting Services server](/sql/reporting-services/install-windows/supported-combinations-of-sharepoint-and-reporting-services-server?view=sql-server-2016&preserve-view=true).
-You can use the Report Viewer web part that has much of the same functionality as integrated mode. for more information, see [Add the Report Viewer web part to a web page](/sql/reporting-services/report-server-sharepoint/add-the-report-viewer-web-part-to-a-web-page?view=sql-server-2017) and [Report Viewer web part on a SharePoint site - Reporting Services](/sql/reporting-services/report-server-sharepoint/report-viewer-web-part-sharepoint-site?view=sql-server-2017)
+You can use the Report Viewer web part that has much of the same functionality as integrated mode. for more information, see [Add the Report Viewer web part to a web page](/sql/reporting-services/report-server-sharepoint/add-the-report-viewer-web-part-to-a-web-page?view=sql-server-2017&preserve-view=true) and [Report Viewer web part on a SharePoint site - Reporting Services](/sql/reporting-services/report-server-sharepoint/report-viewer-web-part-sharepoint-site?view=sql-server-2017&preserve-view=true)
> [!NOTE] > If you want to use Microsoft SQL Server Power Pivot for SharePoint or Microsoft Power View for SharePoint for BI solutions you must install the Power Pivot or Power View add-ins for SQL Server 2016 RTM. The SQL Server 2014 (SP1) Power Pivot for SharePoint and Power View for SharePoint BI solutions do not work with SharePoint Server 2016.
SharePoint Storage And Sql Server Capacity Planning And Configuration https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/storage-and-sql-server-capacity-planning-and-configuration.md
The capacity planning information that we provide contains guidelines to help yo
Learn about [Managing site storage limits for SharePoint in Microsoft 365](../../SharePointOnline/manage-site-collection-storage-limits.md).
-Although tests were not run on SQL Server 2014 (SP1), SQL Server 2016, or SQL Server 2017 RTM you can use these test results as a guide to help you plan for and configure the storage and SQL Server database tier in SharePoint Server 2019, 2016, and 2019 environments. For training about how to configure and tune SQL Server 2012, see [SQL Server 2012 for SharePoint Server 2013](#Section8A). The test results are the same as in SharePoint 2013.
+Although tests were not run on SQL Server 2014 (SP1), SQL Server 2016, SQL Server 2017 RTM, or SQL Server 2019 you can use these test results as a guide to help you plan for and configure the storage and SQL Server database tier in SharePoint Server Subscription Edition, 2019, or 2016 environments. For training about how to configure and tune SQL Server 2012, see [SQL Server 2012 for SharePoint Server 2013](#Section8A). The test results are the same as in SharePoint 2013.
-Because SharePoint Server often runs in environments in which databases are managed by separate SQL Server database administrators, this document is intended for joint use by SharePoint Server farm implementers and SQL Server database administrators. It assumes significant understanding of both SharePoint Server and SQL Server.
+This document is intended for joint use by SharePoint Server farm implementers and SQL Server database administrators as SharePoint Server often runs in environments in which databases are managed by separate SQL Server database administrators. It assumes significant understanding of both SharePoint Server and SQL Server.
This article assumes that you are familiar with the concepts that are presented in [Capacity management and sizing for SharePoint Server 2013](capacity-management-and-sizing-for-sharepoint-server-2013.md).
-## Design and configuration process for SharePoint Servers 2016 and 2019 storage and database tier
+## Storage and database tier design and configuration process for SharePoint Server 2016 and newer
We recommend that you break the storage and database tier design process into the following steps. These sections provide detailed information about each design step, including storage requirements and best practices:
In this section:
<a name="section1a"> </a> ### Databases used by SharePoint Server
-The databases that are installed with SharePoint Servers 2016 and 2019 depend on the service applications that are used in the environment. All SharePoint Server environments rely on the SQL Server system databases. This section provides a summary of the databases installed with SharePoint Servers 2016 and 2019. For detailed database information, see [Database types and descriptions in SharePoint Server](../technical-reference/database-types-and-descriptions.md).
+The databases that are installed with SharePoint Servers (Subscription Edition, 2019, or 2016) depend on the service applications that are used in the environment. All SharePoint Server environments rely on the SQL Server system databases. This section provides a summary of the databases installed with SharePoint Servers. For detailed database information, see [Database types and descriptions in SharePoint Server](../technical-reference/database-types-and-descriptions.md).
Some SharePoint Server, SQL Server Database Engine, and SQL Server Reporting Services (SSRS) databases have specific location recommendations or requirements. For information about these database locations, see [Database types and descriptions in SharePoint Server](../technical-reference/database-types-and-descriptions.md). The **Quick reference guide: SharePoint Servers 2016 and 2019 Databases**, is available to download as either a [PDF](https://download.microsoft.com/download/7/9/7/79700E8E-9896-4657-B9E6-4940B295B71A/DBrefguideSPS2019_tabloid.pdf) or [Visio](https://download.microsoft.com/download/7/9/7/79700E8E-9896-4657-B9E6-4940B295B71A/DBrefguideSPS2019_tabloid.vsdx) file.
The following SharePoint Server features can affect the size of content database
- Based on the space that you want to allocate, determine the number of days of audit logs you want to keep. > [!NOTE]
-> Office Online Server is the next version of Office Web Apps Server. Using Office Online Server with SharePoint Servers 2016 and 2019 doesn't affect the size of the content database. To deploy Office Online Server in your SharePoint Server 2016 farm, see [Deploy Office Online Server](/officeonlineserver/deploy-office-online-server).
+> Office Online Server is the next version of Office Web Apps Server. Using Office Online Server with SharePoint Servers 2016, 2019, Subscription Edition doesn't affect the size of the content database. To deploy Office Online Server in your SharePoint Server 2016 farm, see [Deploy Office Online Server](/officeonlineserver/deploy-office-online-server).
#### Estimate content database IOPS requirements
-IOPS requirements for content databases vary based on how your environment is being used, available disk space, and the number of servers that you have. In general, we recommend that you compare the predicted workload in your environment to one of the solutions that we tested. For more information, see [Performance and capacity test results and recommendations (SharePoint Server 2013)](performance-and-capacity-test-results-and-recommendations-for-sharepoint-2013.md).
+IOPS requirements for content databases vary based on how your environment is being used, available disk space, and the number of servers that you have. In general, we recommend that you compare the predicted workload in your environment to one of the solutions that we tested. For more information and can be applied to newer version of SharePoint, see [Performance and capacity test results and recommendations (SharePoint Server 2013)](performance-and-capacity-test-results-and-recommendations-for-sharepoint-2013.md).
In tests, we found that the content databases tend to range from 0.05 IOPS/GB to around 0.2 IOPS/GB. We also found that a best practice is to increase the top-end to 0.5 IOPS/GB. This increased proportion is more than necessary and can be much more than you'll need in your environment. If you use mirroring, this increased proportion results in much more IO than the primary content databases. Be aware that the mirrored content databases are never lightweight.
After you estimate content storage and IOPS needs, you must determine the storag
#### SharePoint Server service application storage and IOPS requirements <a name="Section1c2"> </a>
-To estimate the storage requirements for the service applications in the system, you must first be aware of the service applications and how you'll use them. Service applications that are available in SharePoint Server 2016 and that have databases are listed in the following tables. The storage and IOPs' data for all of the service applications in SharePoint Servers 2016 and 2019 remains the same as in SharePoint Servers 2010 and 2013.
+To estimate the storage requirements for the service applications in the system, you must first be aware of the service applications and how you'll use them. Service applications that are available in SharePoint Server 2016 and that have databases are listed in the following tables. The storage and IOPS data for all of the service applications in SharePoint Server Subscription Edition, 2019, or 2016 remains the same as in SharePoint Servers 2010 and 2013.
**Search service application storage and IOPS requirements**
To estimate the storage requirements for the service applications in the system,
|State Service <br/> |The State service application has one database. We recommend that you allocate 1 GB for it. It has minimal IOPS. <br/> | |Word Automation Services <br/> |The Word Automation service application has one database. We recommend that you allocate 1 GB for it. It has minimal IOPS. <br/> | |PerformancePoint Services <br/> |The PerformancePoint service application has one database. We recommend that you allocate 1 GB for it. It has minimal IOPS. <br/> |
-|Business Data Connectivity service <br/> |The Business Data Connectivity service application has one database. This database is small and significant growth is unlikely. It has minimal IOPS. <br/> |
+|Business Data Connectivity service <br/> |The Business Data Connectivity service application has one database. This database is small and significant growth is unlikely. It has minimal IOPS. The PerformancePoint Services is not applicable for Subscription Edition. <br/> |
|App Management <br/> |The App Management service application has one database. This database is small and significant growth is unlikely. It has minimal IOPS. <br/> | |Power Pivot <br/> |The Power Pivot Service application has one database. This database is small and has no significant I/O impact. We recommend that you use the same IOPS as the SharePoint content database. Content databases have significantly higher I/O requirements than the Power Pivot service application database. <br/> |
To estimate the storage requirements for the service applications in the system,
<a name="Section1d"> </a> ### Determine availability needs
-Availability is how much a SharePoint Server 2016 environment is perceived by users to be available. An available system is a system that is resilient ΓÇö that is, incidents that affect service occur infrequently, and timely and effective action is taken when they do occur.
+Availability is how much a SharePoint Server environment is perceived by users to be available. An available system is a system that is resilient ΓÇö that is, incidents that affect service occur infrequently, and timely and effective action is taken when they do occur.
Availability requirements can significantly increase your storage needs. For detailed information, see [Create a high availability architecture and strategy for SharePoint Server](plan-for-high-availability.md). Also, see the SQL Server 2012 white paper [AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solutions by Using AlwaysOn Availability Groups](/previous-versions/sql/sql-server-2012/jj191711(v=msdn.10)). <a name="Section2"> </a> ## Choose SQL Server version and edition
-We recommend that for SharePoint Servers 2016 and 2019 you consider running your environment on the Enterprise Edition of the following SQL Servers to take advantage of the other performance, availability, security, and management capabilities that these versions provide.
+We recommend that for SharePoint Server Subscription Edition, 2019, or 2016 you consider running your environment on the Enterprise Edition of the following SQL Servers to take advantage of the other performance, availability, security, and management capabilities that these versions provide.
-- SQL Server 2014 with Service Pack 1 (SP1) (SharePoint Server 2016 only)
+- SQL Server 2019 (SharePoint Subscription Edition, 2019, and 2016)
-- SQL Server 2016 (SharePoint Servers 2016 and 2019)
+- SQL Server 2017 RTM (SharePoint Servers 2016 and 2019)
-- SQL Server 2017 RTM (SharePoint Servers 2016 and 2019)
+- SQL Server 2016 (SharePoint Servers 2016 and 2019)
+
+- SQL Server 2014 with Service Pack 1 (SP1) (SharePoint Server 2016 only)
-For more information about the benefits of these versions, see [Features Supported by the Editions of SQL Server 2014](https://go.microsoft.com/fwlink/?LinkID=808793&amp;clcid=0x409), [Editions and supported features of SQL Server 2016](/sql/sql-server/editions-and-components-of-sql-server-2016), and [Editions and supported features of SQL Server 2017](/sql/sql-server/editions-and-components-of-sql-server-2017).
-
+For more information about the benefits of these versions, see [Features Supported by the Editions of SQL Server 2014](https://go.microsoft.com/fwlink/?LinkID=808793&amp;clcid=0x409), [Editions and supported features of SQL Server 2016](/sql/sql-server/editions-and-components-of-sql-server-2016), [Editions and supported features of SQL Server 2017](/sql/sql-server/editions-and-components-of-sql-server-2017), and [https://docs.microsoft.com/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15](/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15&preserve-view=true)).
++ We recommend that for SharePoint Server 2013 you consider running your environment on the Enterprise Edition of SQL Server 2008 R2 with Service Pack 1 (SP1), SQL Server 2012, or SQL Server 2014 to take advantage of the other performance, availability, security, and management capabilities that these versions provide. For more information about the benefits of SQL Server 2008 R2 with SP1, SQL Server 2012, and SQL Server 2014 Enterprise Edition, see [Features Supported by the Editions of SQL Server 2014](https://go.microsoft.com/fwlink/?LinkID=808793&amp;clcid=0x409), [Features Supported by the Editions of SQL Server 2012](/previous-versions/sql/sql-server-2012/cc645993(v=sql.110)), and [Features Supported by the Editions of SQL Server 2008 R2](/previous-versions/sql/sql-server-2008-r2/cc645993(v=sql.105)). In particular, you should consider your need for the following features: -- **Backup compression** Backup compression can speed up any SharePoint backup, and is available in every edition of SQL Server 2008 and later. By setting the compression option in your backup script, or by configuring the server that is running SQL Server to compress by default, you can significantly reduce the size of your database backups and shipped logs. For more information, see [Backup Compression (SQL Server)](/sql/relational-databases/backup-restore/backup-compression-sql-server) for SQL Server 2014 and [Backup Compression (SQL Server)](/sql/relational-databases/backup-restore/backup-compression-sql-server) for SQL Server 2016 and SQL Server 2017 RTM.
+- **Backup compression** Backup compression can speed up any SharePoint backup, and is available in every edition of SQL Server 2008 and later. By setting the compression option in your backup script, or by configuring the server that is running SQL Server to compress by default, you can significantly reduce the size of your database backups and shipped logs. For more information, see [Backup Compression (SQL Server)](/sql/relational-databases/backup-restore/backup-compression-sql-server).
> [!NOTE] > SQL Server data compression is not supported for SharePoint Server, except for the Search service application databases.
In particular, you should consider your need for the following features:
> If you are using a Remote BLOB storage provider that does not support database snapshots, you can't use snapshots for content deployment or backup. - **Remote BLOB storage** If you want to take advantage of remote BLOB storage to a database or location outside the files associated with each content database, you must use the Enterprise Edition of: ++
+ **SharePoint Server Subscription Edition**
+
+ - SQL Server 2016
+
+ - SQL Server 2017 RTM
+
+ - SQL Server 2019
**SharePoint Server 2019**
- - SQL Server 2016
+ - SQL Server 2016
+
+ - SQL Server 2017 RTM
- - SQL Server 2017 RTM
+ - SQL Server 2019
**SharePoint Server 2016**
- - SQL Server 2014 (SP1)
+ - SQL Server 2014 (SP1)
- - SQL Server 2016
+ - SQL Server 2016
- - SQL Server 2017 RTM
+ - SQL Server 2017 RTM
+
+ - SQL Server 2019
**SharePoint 2013**
- - SQL Server 2008 R2 with SP1
+ - SQL Server 2008 R2 with SP1
- - SQL Server 2012 Enterprise Edition
+ - SQL Server 2012 Enterprise Edition
-- **Resource governor** Resource Governor is a technology introduced in SQL Server 2008 to enable you to manage SQL Server workloads and resources by specifying limits on resource consumption by incoming requests. Resource Governor enables you to differentiate workloads and allocate CPU and memory as they are requested, based on the limits that you specify. For more information about how to use Resource Governor, see [Resource Governor](/sql/relational-databases/resource-governor/resource-governor) for SQL Server 2014 and [Resource Governor](/sql/relational-databases/resource-governor/resource-governor) for SQL Servers 2016 and 2019.
+- **Resource governor** Resource Governor is a technology introduced in SQL Server 2008 to enable you to manage SQL Server workloads and resources by specifying limits on resource consumption by incoming requests. Resource Governor enables you to differentiate workloads and allocate CPU and memory as they are requested, based on the limits that you specify. For more information about how to use Resource Governor, see [Resource Governor](/sql/relational-databases/resource-governor/resource-governor).
We recommend that you use Resource Governor with SharePoint Server to:
In particular, you should consider your need for the following features:
- Monitor how many resources are consumed by each database in the system ΓÇö for example, you can use Resource Governor to help you determine the best placement of databases among computers that are running SQL Server. -- **Microsoft Power Pivot for SharePoint** Enables users to share and collaborate on user-generated data models and analysis in Excel on the web while automatically refreshing those analyses. You must have Office on the web to use Excel on the web with Power Pivot for SharePoint and SharePoint Server 2016. You can use SQL Server 2014 (SP1) or SQL Server 2016 RTM Enterprise Edition and SQL Server Analysis Services for business intelligence with SharePoint Server 2016. However, you can only use Power Pivot for SharePoint with SQL Server 2016 RTM, not with SQL Server 2014 (SP1).
+- **Microsoft Power Pivot for SharePoint** Enables users to share and collaborate on user-generated data
+models and analysis in Excel on the web while automatically refreshing those analyses. You must have
+Office on the web to use Excel on the web with Power Pivot for SharePoint and SharePoint Server 2016.
+You can use SQL Server 2014 (SP1) or SQL Server 2016 RTM Enterprise Edition and SQL Server Analysis
+Services for business intelligence with SharePoint Server 2016. However, you can only use Power Pivot
+for SharePoint with SQL Server 2016 RTM, not with SQL Server 2014 (SP1).
- **Power Pivot for SharePoint 2013** Enables users to share and collaborate on user-generated data models and analysis in Excel and in the browser while automatically refreshing those analyses. It is part of SQL Server 2008 R2 Analysis Services (SSAS) Datacenter and Enterprise Edition, SQL Server 2012 SP1 Analysis Services (SSAS) Enterprise Edition, and SQL Server 2014 Analysis Services (SSAS) Enterprise and Business Intelligence Edition.
The following guidance describes best practices to plan for as you configure eac
#### Separate and prioritize your data among disks
-Ideally, you should place the tempdb database, content databases, Usage database, search databases, and SQL Server 2014 (SP1), SQL Server 2016, SQL Server 2017 RTM, SQL Server 2008 R2 with SP1 and SQL Server 2012 transaction logs on separate physical hard disks.
+Ideally, you should place the tempdb database, content databases, database, search databases, and SQL Server 2019, SQL Server 2017 RTM, SQL Server 2016, SQL Server 2014 (SP1), SQL Server 2012, and SQL Server 2008 R2 with SP1 transaction logs on separate physical hard disks.
The following list provides some best practices and recommendations for prioritizing data:
Test that your performance and backup solution on your hardware enables you to m
Test the backup solution that you are using to make sure that it can back up the system within the available maintenance window. If the backup solution can't meet the SLAs your business requires, consider using an incremental backup solution such as Microsoft System Center Data Protection Manager.
-It is important to track the following resource components of a server that is running SQL Server: CPU, memory, cache/hit ratio, and I/O subsystem. When one or more of the components seems slow or overburdened, analyze the appropriate strategy based on the current and projected workload. For more information, see [Monitor and Tune for Performance](/sql/relational-databases/performance/monitor-and-tune-for-performance) for SQL Server 2014 (SP1) and [Monitor and Tune for Performance](/sql/relational-databases/performance/monitor-and-tune-for-performance) for SQL Server 2016 and SQL Server 2017 RTM.
+It is important to track the following resource components of a server that is running SQL Server: CPU, memory, cache/hit ratio, and I/O subsystem. When one or more of the components seems slow or overburdened, analyze the appropriate strategy based on the current and projected workload. For more information, see [Monitor and Tune for Performance](/sql/relational-databases/performance/monitor-and-tune-for-performance).
The following section lists the performance counters that we recommend that you use to monitor the performance of the SQL Server databases that are running in your SharePoint Server environment. Also listed are approximate healthy values for each counter.
For more information and memory troubleshooting methods, see the following resou
- [Monitor CPU Usage](/sql/relational-databases/performance-monitor/monitor-cpu-usage) -- **SQL Server 2016 &amp; SQL Server 2017 -**[Monitor Memory Usage](/sql/relational-databases/performance-monitor/monitor-memory-usage)
+- **SQL Server 2017, SQL Server 2017, & SQL Server 2019 -**[Monitor Memory Usage](/sql/relational-databases/performance-monitor/monitor-memory-usage)
- [Monitor Disk Usage](/sql/relational-databases/performance-monitor/monitor-disk-usage)
SharePoint Software Boundaries Limits 2019 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/software-boundaries-limits-2019.md
description: "Learn about the tested performance and capacity limits of SharePoi
# Software boundaries and limits for SharePoint Servers 2016 and 2019 This article describes software boundaries and limits of SharePoint Servers 2016 and 2019 which include: