Summary: Piotr Gardy, a Microsoft Premier Field Engineer based in Poland, provides us with recommendations on why (and how) a ConfigMgr database should be hosted on its own dedicated SQL Server instance. For more useful tidbits, please check out Piotr’s Polish language TechNet blog.
When you perform following operations with System Center Configuration Manager (a.k.a. ConfigMgr):
it may require a restart of the SQL Server service that hosts (or will host) the Configuration Manager database. The setup won’t ask you to restart the service, but you can note that a restart is required in the following log file: C:\ConfigMgrSetup.log.
A problem with this is that a restart of the SQL service can result in downtime for other services which host their databases on the same SQL Server instance.
What would I recommend in such a case?
Hope this helps!
Written by Piotr Gardy; Posted by Frank Battiston, MSPFE Editor