SQL Server Requirements for System Center 2012 R2
Updated: May 13, 2016
Applies To: System Center 2012 R2
Use this information to evaluate if your SQL Server environment is ready to support the installation of or upgrade to System Center 2012 R2. Use this information whether you are deploying one or multiple components of System Center.
SQL Server 2012 SP2 is only supported as a database server for installations with Update Rollup 4 applied, except for Operations Manager which supports SQL Server 2012 SP2 without requiring any update rollups.
SQL Server 2014 is only supported as a database server for installations of Orchestrator, SPF and Virtual Machine Manager with Update Rollup 5 applied.
SQL Server 2014 is only supported as a database server for installations of Data Protection Manager (DPM), and Service Manager with Update Rollup 6 applied. A new installation of DPM 2012 R2 cannot work with SQL Server 2014. To use SQL Server 2014 with DPM 2012 R2, you must install DPM 2012 R2 with SQL Server 2012, and then upgrade to SQL Server 2014.
No Update Rollups are required to use SQL Server 2014 as the database Server for Operations Manager.
In the table below all entries for Operations Manager refer to both the Operations Manager database as well as the Audit Collection Services database.
Virtual Machine Manager supports the currently supported Service Pack of SQL Server. This support applies to VMM 2007, VMM 2008, VMM 2008 R2, VMM 2012, and VMM 2012 R2.
|System Center 2012 R2 component||SQL Server 2008 R2 SP1 Standard, Datacenter||SQL Server 2008 R2 SP2 Standard, Datacenter||SQL Server 2008 R2 SP3 Standard, Datacenter*||SQL Server 2012 Enterprise, Standard (64-bit)||SQL Server 2012 SP1 Enterprise, Standard (64-bit)||SQL Server 2012 SP2 Enterprise, Standard (64 bit)||SQL Server 2012 SP3 Enterprise, Standard (64 bit)||SQL Server 2014 Enterprise, Standard (64-bit)||SQL Server 2014 SP1 Enterprise, Standard (64-bit)|
|App Controller Server||●||●||●|
|Data Protection Manager (DPM) Database||●||●||●||●||●||●||●||●||●|
|Operations Manager Data Warehouse||●||●||●||●||●||●||●||●||●|
|Operations Manager Operational Database||●||●||●||●||●||●||●||●||●|
|Operations Manager Reporting Server||●||●||●||●||●||●||●||●||●|
|Orchestrator Management Server||●||●||●||●||●||● (Since UR8)||●||●|
|Service Management Automation Management Server||●||●||●||● (Since UR7)||●||●|
|Service Manager Database or Data Warehouse Database||●||●||●||●||●||● (Since UR9)||●||●|
|Service Provider Foundation||●||●||●||●|
|Virtual Machine Manager Database Server||●||●||●||●||●||●|
* If you plan to use SQL Server 2008 R2 SP3 to host your Operations Manager Operational, Reporting Server, or Data Warehouse databases for a new Operations Manager installation you must first install with SQL Server 2008 R2 SP2, and then upgrade SQL Server 2008 R2 to the SP3 version.
This information describes general recommendations for SQL Server regardless of what System Center component you are deploying.
You will need a minimum of four computers to deploy all System Center components. Aside from performance reasons, not all system components can coexist on the same computer. For more information, see Component Coexistence.
For testing purposes only, one SQL Database Engine Services instance may be used for all components, but is not recommended in a production setting due to performance concerns.
Reporting Services instances cannot be shared between System Center components.
SQL_* collations are being deprecated for their Windows equivalents.
Limit the memory of each SQL Server instance such that the Total Memory setting allows a minimum of 1 GB (2GB preferred) of free memory after all services are running.
System Center components requiring the most disk resources are Service Manager, Operations Manager and Configuration Manager.
Disks used should be formatted to a 64K allocation unit size.
Disks used should be configured to allow 20% free space after all calculations for monitoring. Set growth upper limits to not exceed this space limit.
Pre-sizing is preferred - use auto-grow if needed as it uses more resources.
Set Pre-size to 8GB/2GB as a minimum. 20-30% of the database file size is a rule of thumb.
Set Auto-grow to 500/100 as a minimum.
This information does not apply to System Center 2012 Configuration Manager. For those system requirements, see Supported Configurations for Configuration Manager.
System Requirements for System Center 2012 R2
Preparing your environment for System Center 2012 R2 App Controller
Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)
Preparing your environment for System Center 2012 R2 Operations Manager
Preparing your environment for System Center 2012 R2 Orchestrator
Preparing your environment for System Center 2012 R2 Service Manager
Preparing your environment for System Center 2012 R2 Service Provider Foundation
Preparing your environment for System Center 2012 R2 Virtual Machine Manager