It’s well known that SQL takes as much memory as it can, and several experts
tell us to manually set the memory size to xxx. But what number should I
use for xxx? I often see “100” as the example. I assume this means 100MB.
But why that number? How could I be more methodical in picking a number?
In the SQL 2005 Enterprise Manager that comes with the Premium Edition, I
can pick a SQL instance, choose properties, and select the ‘Memory’ page.
Can I get the same result by entering 100 in the field called “Maximum
server memory (in MB)”? What is the recommend Maximum and Minimum for:
Thanks for your help in fixing the slowness of some services.
Can’t tell you what max/min is but here’s what’s worked for me on a 4 gig box:
Your mileage may vary and bump it around if need be. I can’t tell you the minimum
and maximums as each server may be different.
All I can tell you is what worked on mine. (edited in the SMBnation.com session)
Also make sure you aren’t seeing a bogus allocated memory where you added more RAM and
forgot to bump up the performance counters – http://blogs.technet.com/sbs/archive/2006/06/07/433707.aspx
After I added WSUS 3.0 I did bump up those counters a bit rather than worry about throttle memory
use so much.
Bottom line make sure you really NEED to stomp on memory use or not. Watch that
task manager and review your daily email report to see if it’s really and truly needed
that something is growing and growing and not settling down like it should.
And yes, you can use the GUI and not the command line to do all of this.
For reference, Dr. J’s memory post on WSUS is here:
P.S. I just built a new category called “Allocated Memory”