Question : sqlserver.exe is RAM greedy.

In SBS2008, which has SQL Server 2005, sqlserver.exe is too RAM greedy.

Apparently this behavior is by design, but sqlserver.exe is sucking up 2.5GB of RAM just to run the $SBSMONITORING database, which is a complete waste.

I have lowered the max memory values in SQL Management Studio, but that hasn't worked yet. I restarted the service thinking that would lower the memory usage and use the new values.

No joy.

I'll give it 512MB of RAM to run, but not 2.5GB.

How do I lower this amount of RAM usage?

Answer : sqlserver.exe is RAM greedy.

Only used to be if the following situation applies:

"Note In WSUS 3.0, the client changes its SusClientID if the hardware configuration changes. For Windows Vista, for Windows Server 2008, and for later versions, Sysprep is changed to reset the SusClientID. Therefore, this problem affects only virtual machines that run pre-Windows Vista operating systems, or that were not created by using Sysprep."


So for systems that are hosted in VMware or HyperV this can still be a big problem, especially with pre-Vista/2008 sysprep.   Your suggestion does not help him diagnose the issue to see if it is something as simple as a failure in GPO settings.