Configure SQL for new ConfigMan 2012 R2 installation?

I will be installing the a single-server SCCM 2012 R2 for a small environment.  I will use SQL 2012 or 2014 (not sure if upgrade from SQL 2012 to SQL 2014 is included in the SCCM package purchased) and everything will be on a single Server 2012 R2 with 2 SSD drives in RAID 1.  I plan to partition the C drive for Windows and then SQL and SCCM will all run on the D partition on the SSD.

The instructions I have found for installing System Center Configuration Manager 2012 R2 didn't go into much detail on setting up SQL other than configuring the maximum RAM setting.

Are there any recommended SQL configuration optimizations for a new SQL install that will be used only for Config Manager 2012 R2?

What about recommended scheduled maintenance and backup tasks?



  • Edited by MyGposts Wednesday, August 26, 2015 2:01 AM
August 26th, 2015 1:59am

To prevent the C drive from running out of space based on any future growth of the database. 

Having separate partitions will protect the free space on the C drive.

I double checked the drives and it will be 3 480GB drives, so it will need to be RAID 5 instead of RAID 1.

It will just be a few hundred clients.
  • Edited by MyGposts Wednesday, August 26, 2015 5:57 AM
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2015 5:53am
I was told before that protecting the system drive from running out of disk space is more important than protecting Config Manager and SQL from running out of space. Over time Config Manager is going to grow as more packages and patches are added. The disk partition separating the system drive from everything else would prevent the growth from crowding the system drive and preventing the server from functioning at all. Also, partitons can be adjusted later by shrinking and expanding. If it is all one giant C drive and it fills unexpectedly, that is a bigger problem than the partition SCCM is running on running out of space. What other options are there on a server with 3 drives?
  • Edited by MyGposts 18 hours 27 minutes ago
August 26th, 2015 9:24am
That's not the best hardware to install ConfigMgr on. Either you accept those limitations or buy new hardware. (I'd use a single partition in this scenario if I would have to stick with this hardware)
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2015 9:41am
That's what file growth limitations in SQL server are for. Creating partitions actually wastes space because let's say your database does grow and consumes all of the D volume but you still have 100GB free on the C volume doing absolutely nothing. You've just artificially caused yourself to run out of space when there actually was space available. Initially sizing your DB correctly and setting limits will prevent al
August 26th, 2015 4:01pm
That's not the best hardware to install ConfigMgr on. Either you accept those limitations or buy new hardware. (I'd use a single partition in this scenario if I would have to stick with this
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2015 4:02pm

How are file growth limitations set in SQL?

In the properties of the database.
August 26th, 2015 4:16pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics