TrialandError Posted June 10, 2016 Report post Posted June 10, 2016 I am preparing to migrate from an over specced 2012 R2 hierarchy to a Stand alone primary running 1602 and wanted to get some opinions\feedback from the community before I finalized anything. I am undecided on whether or not to install sql on its own server or just install it on the site server. I know best practices used to be to install sql and config manager on the same server but wasn't sure if that was still the case. Quote Share this post Link to post Share on other sites More sharing options...
sumyun Posted June 10, 2016 Report post Posted June 10, 2016 There are lots to consider and discuss, but I found this TechEd article from 3 years ago still a very good reference. http://www.derekseaman.com/2013/06/teched-2013-system-center-config-mgr-2012-sp1.html There are some other web discussion on how to setup the SQL database, log files, and tempDB. I am working in an environment with about 30k clients, extremely satisfy with SQL and Primary site on the same server. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 10, 2016 Report post Posted June 10, 2016 In all but rare cases, SQL should be local to CM. As for what drives DB, Log etc. should live on that question, can only be answered after understanding exactly how your server is setup.. If for example you have a VM and all the VHDs exist on the same physical disks then there is ZERO point is splitting up db, logs, etc. Quote Share this post Link to post Share on other sites More sharing options...
TrialandError Posted June 11, 2016 Report post Posted June 11, 2016 Thanks guys - local it is! Quote Share this post Link to post Share on other sites More sharing options...
