I have run into several SB installs with very high memory utilization issues lately. I started poking around and noticed it was MS SQL chewing up all the memory. I thought this was odd so I hit good old google and sure enough it is a very common issue for WSUS to go a bit crazy on the memory consumption. the following article will help you correct thee issue and have your server running lean and clean in no time.
Our destination SBS 2011 has an SQL (S-Q-L) process that was taking up a whopping 5GB of RAM:
Since this was a relatively fresh install of SBS 2011 we needed to find out what SQL setup was using so much memory.
Open Task Manager –> Processes tab.
View –> Choose Columns –> PID, Memory, etc. (Our SBS 2011 Setup Guide has the customizations)
Start –> CMD –> Right click and Run As Admin.
tasklist /svc [Enter]
Scroll through the resulting list looking for the PID.
Start –> All Programs –> Microsoft SQL Server 2008 R2 –> Right click and Run as Admin on SQL Server Management Studio.
Server type: Database Engine.
Server name: \\.\pipe\mssql$microsoft##ssee\sql\query
Copy and paste the above.
Authentication: Windows Authentication.
Click Connect.
Right click the root node (\\.\pipe\mssql$microsoft##ssee\sql\query) and left click on Properties.
Click Memory.
Change the amount of memory that WSUS can use. On this particular SBS 2011 VM we have 16GB of RAM allocated. So, we will set the amount of RAM to 1GB.
Before:
After:
Our WSUS SQL memory usage was now a lot more reasonable:
the information in this article is from another blog located here