YCOE Staff
asked on
What is the best practice for running SCCM 2016 and SQL 2016
When running SCCM 2016 and SQL 2016 what is the best practice for running these two servers? Should run both SCCM and SQL on the same server? Or should these be on two different servers?
Vitor Montalvão
If possible run both services in separate servers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you want to run both services in a single server I will recommend you to have a server with enough resources (CPU and RAM) to support both services.
Just a note that you will likely get different answers from DBAs and non-DBAs, but in short since SCCM includes a license for SQL server I think it makes sense to put it on the same system since you eliminate the network bottleneck.
ASKER
Thank you everyone to who has responded. And you're right I am seeing a mix of yes and no's. So what is the pros and cons of running the SQL and SCCM on the same server? And for the folks that say run them on different servers what is the reasoning behind that?
My background: I'm really new to SCCM and SQL so that's why I'm asking these questions. Just trying to better understand it. So I appreciate your time explaining it to me!
My background: I'm really new to SCCM and SQL so that's why I'm asking these questions. Just trying to better understand it. So I appreciate your time explaining it to me!
Pros: Better performance
Cons: Need to allocate more RAM/CPU/disk to one server
Yet another SQL server to manage
Cons: Need to allocate more RAM/CPU/disk to one server
Yet another SQL server to manage
ASKER
Thank you to everyone for your comments / suggestions!
Hi,
I know Adam has already answered but I want to add a +1 to his comments.
Putting CM + SQL on different boxes just adds a layer of complexity + reduction in speed + potential for network outage.
And you also have the expense of another box to buy and care for.
Aside from that the other tip which answers the "Performance of SQL + CM" is to not rely on the CM Reindexing task alone. It's fine (tick it) but it needs more help, so many people run this tuning script by Ola Hallengren:
https://ola.hallengren.com/sql-server-backup.html
Mike
I know Adam has already answered but I want to add a +1 to his comments.
Putting CM + SQL on different boxes just adds a layer of complexity + reduction in speed + potential for network outage.
And you also have the expense of another box to buy and care for.
Aside from that the other tip which answers the "Performance of SQL + CM" is to not rely on the CM Reindexing task alone. It's fine (tick it) but it needs more help, so many people run this tuning script by Ola Hallengren:
https://ola.hallengren.com/sql-server-backup.html
Mike
Hi,
I have tried booth solutions but I prefer the SQL on the same server as SCCM.
The network bottleneck and extra license cost is not worth it, as long as you have good specs on the server.
It is a good idea to config SQL so it can utilize more RAM.
Just ask me if you want help with howto configure that.
Also see this:
https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/recommended-hardware
I have tried booth solutions but I prefer the SQL on the same server as SCCM.
The network bottleneck and extra license cost is not worth it, as long as you have good specs on the server.
It is a good idea to config SQL so it can utilize more RAM.
Just ask me if you want help with howto configure that.
Also see this:
https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/recommended-hardware