How can I reduce the amount of memory usage for the Windows Internal Database MICROSOFT##SSEE (WSUS) on my SBS2003R2 server?
Hi experts,
We have a single SBS2003R2 DC running basically everything (unfortunately). SQL Server is running Exchange, WSUS 3.0, Sharepoint, Backup Exec.
System Specs:
SBS 2003 32-bit
Dual Core Xeon 5130 CPU x 2
4 GB RAM (recognizing 3,582 MB)
3 x 500GB Raid 5 as a single drive
We have approximately 40 windows XP clients utilizing the server but not all are connected to the network at once. Our consultants use laptops and are not always in the office so server load is generally low.
For quite some time now, I have been noticing very high memory usage (allocated memory) through the SBS Monitoring performance report. I've discovered that my Internal Database (MICROSOFT##SSEE), which I assume is WSUS 3.0, has almost 1 GB of allocated memory. I somehow don't think that's right! The next highest usage is:
Exchange Store using 600MB
SBS Monitoring Database using 155MB
is there a way to reduce the memory usage of the internal database?? I've included the top 9 processes in a TEXT file. I used Process Explorer to get this info.
Thank you for your responses!
4-9-09-process-explorer.txt
We have a single SBS2003R2 DC running basically everything (unfortunately). SQL Server is running Exchange, WSUS 3.0, Sharepoint, Backup Exec.
System Specs:
SBS 2003 32-bit
Dual Core Xeon 5130 CPU x 2
4 GB RAM (recognizing 3,582 MB)
3 x 500GB Raid 5 as a single drive
We have approximately 40 windows XP clients utilizing the server but not all are connected to the network at once. Our consultants use laptops and are not always in the office so server load is generally low.
For quite some time now, I have been noticing very high memory usage (allocated memory) through the SBS Monitoring performance report. I've discovered that my Internal Database (MICROSOFT##SSEE), which I assume is WSUS 3.0, has almost 1 GB of allocated memory. I somehow don't think that's right! The next highest usage is:
Exchange Store using 600MB
SBS Monitoring Database using 155MB
is there a way to reduce the memory usage of the internal database?? I've included the top 9 processes in a TEXT file. I used Process Explorer to get this info.
Thank you for your responses!
4-9-09-process-explorer.txt
ASKER
Thank you MrMintanet for your comment. I'm still concerned about overall memory usage on this machine. As I said, we have 4GB of Physical RAM (recognizing 3,582) and my SBS Monitoring Reports as recently as this morning is showing Memory in use of 3,796 MB!!! I don't believe it should be running this high, do you?
When I reboot the server (for updates, etc.), the memory usage starts off low for a while but then over the course a few days, it creeps back up over 3,500MB.
Is there any better application that I can use to isolate the processes and attach it here for review?
Thanks so much!
When I reboot the server (for updates, etc.), the memory usage starts off low for a while but then over the course a few days, it creeps back up over 3,500MB.
Is there any better application that I can use to isolate the processes and attach it here for review?
Thanks so much!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry, you were typing your last comment while I was typing mine, so I missed it.
The Windows Internal Database is probably one of the only services you need to worry about when it comes to RAM utilisation. Other services, such as the Exchange Store process, are designed to utilise as much RAM as possible, but will release it if another application requires it.
The Windows Internal Database process should apply the same principle, but I usually set a Maximum simply because it only runs WSUS, and doesn't need a LOT of RAM (it's not an intensive mission-critical database server we're talking about here) and ideally want a bit of RAM left in the server for usage on-demand if necessary.
-Matt
What is your PF set to?
PF = Page File
If you are still concerned, get a second server for the SQL. It sounds like there's just far too much going on.
PF = Page File
If you are still concerned, get a second server for the SQL. It sounds like there's just far too much going on.
If the SQL Server is just being used for WSUS and the SBS Monitoring Service, it wouldn't be viable to relocate those services off to a dedicated SQL Server. I'd only suggest that if there is a LoB application which also requires SQL Server and is utilising system resources.
WSUS and SBS Monitoring do not require an inordinate amount of RAM to function; you can safely restrict it per my last comment.
-Matt
ASKER
Thank you both for your comments and suggestions. After following tigermatt's suggestions about limiting the memory usage for WSUS to 512MB, my memory usage dropped to about 3,400MB from 3,800MB. This was most helpful. Can I do the same thing with SBS Monitoring but limit it down to a smaller number like 50MB??
If you wished, you can. Follow the same procedure; just connect to the SBSMONITORING instance in Enterprise Manager.
-Matt
ASKER
tigermatt, by limiting the memory usage to 50MB, will that adversly affect anything with respect to SBSmonitoring?
I'd probably not push it that though - maybe 200MB maximum. But SBS Monitoring isn't particularly SQL Server-intensive, so it doesn't need an inordinate amount of RAM assigned.
-Matt
-Matt
It shouldn't be a problem - Windows processes in general are designed to share memory and use it all if possible. It's almost more worrying to find a busy machine with 4Gb of RAM showing that most of it is unused; it ought to be used for things like caching!