Generally speaking, the more RAM you can allocate to SQL the more it will use, thus the performance should increase when it can use RAM versus disk.  The amount depends on your environment, how many clients, site systems, etc. you have feeding data into SQL, but overall SQL will pretty much use as much memory as you give it.

If you have 32 GB of memory, I would generally recommend saving 4GB for the OS, 4GB for SCCM, the remaining for SQL.  So for your scenario that would be 24 to SQL, the rest for OS/SCCM.

• Marked as answer by skatterbrainz 12 hours 27 minutes ago

Sounds good.  The current load is about 4000 clients and expected to grow to around 6000 within a month or two.

What about settings for Index creation memory and Query memory?  Right now, they're still at defaults of 0 and 1024 (respectively).  Should those be adjusted up also?

• Edited by skatterbrainz Tuesday, June 16, 2015 9:37 PM

I personally haven't found a reason to modify those settings.

Thank you!

I have an SCCM 2012 R2 SP1 standalone primary site server running on a virtual guest with SQL Server 2012 SP2 installed on the same guest.  The two are installed on separate disks, but overall, the guest has 32 GB of memory allocated.  The SQL instance is configured with 8 GB memory min=max.  The resource utilization appears good and fairly consistent, but my question is should I consider increasing the threshold for SQL Server?  

The recommendation posted at https://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSiteRoleReqs is to allocate 50-80 percent of the available memory to SQL.  I'm curious if that will buy me performance gains which I'm not seeing because I'm looking in the wrong place.

Sounds good.  The current load is about 4000 clients and expected to grow to around 6000 within a month or two.

What about settings for Index creation memory and Query memory?  Right now, they're still at defaults of 0 and 1024 (respectively).  Should those be adjusted up also?

• Edited by skatterbrainz 9 hours 52 minutes ago

Generally speaking, the more RAM you can allocate to SQL the more it will use, thus the performance should increase when it can use RAM versus disk.  The amount depends on your environment, how many clients, site systems, etc. you have feeding data into SQL, but overall SQL will pretty much use as much memory as you give it.

If you have 32 GB of memory, I would generally recommend saving 4GB for the OS, 4GB for SCCM, the remaining for SQL.  So for your scenario that would be 24 to SQL, the rest for OS/SCCM.

Just as William says, my general configuration is 4GB for the operating system, 4GB for ConfigMgr, and the rest for SQL.  There should be no issue adjusting SQL's min/max memory setting to utilize more of the memory.

Jeff