System Center 2016 – Operations Manager databases must use the same version of SQL Server, the SQL Server collation setting must be one of the following supported types as described in that section, and SQL Server Full Text Search is required for both the operational and data warehouse databases.
Sizing and configuration of the database server is critical to the overall performance of the management group.
The most critical resource used by the Operations Manager database is the storage subsystem, but CPU and RAM are also significant.
To set up an availability group you'll need to deploy a Windows Server Failover Clustering (WSFC) cluster to host the availability replica, and enable Always On on the cluster nodes.
You can then add the Operations Manager SQL Server database as an availability database.
In addition, the workload put on the Reporting data warehouse by reporting is different than the load put on the Operations Manager database by Operations console usage.
Factors that influence the load on the Reporting data warehouse include: The Operations Manager data warehouse database is a single source of failure for the management group, so it can be made highly available using supported failover configurations such as SQL Server Always On Availability Groups or Failover Cluster Instances.
System Center 2016 - Operations Manager requires access to an instance of a server running Microsoft SQL Server 2012, 2014, or SQL Server 2016 to support the operational, data warehouse, and ACS audit database.
The operational and data warehouse databases are required and created when you deploy the first management server in your management group, while the ACS database is created when you deploy an ACS collector in your management group.
With System Center 2016 - Operations Manager, SQL Always On is preferred over failover clustering to provide high availability for databases.
All databases except the native mode Reporting Services installation, which uses two databases to separate persistent data storage from temporary storage requirements, can be hosted in an Always On Availability Group.
In general, previous deployment experience with customers shows that performance issues are typically not caused by high resource utilization (i.e.