Quite regularly I get asked “Can we use 1 SQL Server or AlwaysOn Cluster for our System Center implementation?” The answer is Yes, HOWEVER, there is some caveats.
- Reporting Services
Service Manager, Operations Manager and Configuration Manager all use a lot of space. I tested this in my lab with the following servers:
- 2 x System Center Configuration Manager Servers
- 5 x System Center Service Manager Servers (2 x Management, 1 x DW, 2 x Self Service Portal)
- 3 x System Center Operations Manager
- 2 x System Center Data Protection Manager Servers
- 3 x System Center Virtual Machine Manager Servers (2 Management, 1 x Library)
- 4 x System Center Orchestrator
Totalling 19 Servers + 4 x SQL (2 x SQL Servers in an AlwaysOn configuration & 2 x Reporting Services Servers)
I wrote about installing SQL for System Center here:
Part 1 – Installing Highly Available SQL 2016 with SP1 for System Center 2016 – Part 1 (SQL Server AlwaysOn Availability Groups)
Part 2 – Installing Highly Available SQL 2016 with SP1 for System Center 2016 – Part 2 (Network Load Balancing Reporting Services)
Part 3 – Installing Highly Available SQL 2016 with SP1 for System Center 2016 – Part 3 (Reporting Services on a SQL Cluster)
The size of the DB’s based on this configuration was:
- System Center Service Manager: 24 GB
- System Center Operations Manager: 11 GB
- System Center Configuration Manager: 7 GB
- System Center Data Protection Manager: 1 GB
- System Center Virtual Machine Manager (VMM): 260 MB
- System Center Orchestrator: 600 MB
IOPS is also a major consideration. Don’t be surprised to find 2000+ IOPS required if you collocate all the components DB’s on one server!
Probably the main consideration is you must use a dedicated instance of SQL Server Reporting Services for each component that uses Reporting Services which I wrote about here.
The following guides should help you plan your deployment:
Planning for Hardware Configurations for Configuration Manager – https://technet.microsoft.com/en-us/library/hh846235.aspx
System Requirements: VMM Database in System Center 2012 and in System Center 2012 SP1 – https://technet.microsoft.com/en-us/library/gg610574.aspx (Still relevant for 2016)
System Center Operations Manager Sizing Helper Tool – http://download.microsoft.com/download/C/A/6/CA60425C-950B-456E-986C-C5F2FCD5668D/System%20Center%202012%20Operations%20Manager%20Sizing%20Helper%20Tool%20v1.xls
Technical Documentation Download for System Center 2012 – Service Manager – https://www.microsoft.com/en-gb/download/details.aspx?id=27850
Is it wise to use a common SQL server for multiple components of System Center 2016? it all comes down to budget, you can, but ensure you consider the requirements of each component and see the guidance above for sizing general recommendations.