SBS 2003 RAM maxed out by sql server

Check your disk space you might be running low on "resources" which is when your system tries to swap out some RAM to disc and cannot find sufficient disk space to increase the swap file size.  Try making a manual swap file lik 4gig or something big.

Simply going into the system p[roperties and looking at performance and acting as IF you were going to create a large manual swap file should give you the answer if disk space has anything to do with it all.  

The other thing you can do it run the defrag.

Try these tuning recommendations from Microsoft.

http://www.microsoft.com/technet/prodtechnol/sppt/sharepoint/maintain/optimize/spsperft.mspx#EEAA

that's a quick response! thanks.

SBS= Small Business Server.
store.exe is the mailbox info store for Exchange.
Small Business Server 2003 includes MS Exchange, Sharepoint Services, and Windows Server. We also have Symantec Mail Security for Exchange running on this machine, which takes up a significant amount of RAM on its own.

sqlserver.exe is currently taking about 550MB, store.exe is currently taking about 580MB

In response to Informative, I'm sure we have enough disk space.

Since SBS is a package deal, i didn't install SQL server separately, and so I don't think I have Enterprise Manager.

I was just wondering what it is used for, so I coud tell what might be causing this memory drain. Previously, it wasn't taking up that much space at all. and I think the only thing we've really changed is that we've added some to the sharepoint site.

However, I did muck about with registration of sqlvdi.dll about a week ago, because of another problem we have been having with backup and certserve. I wondered if something I did there might have caused a problem.

thanks for the quick responses.

ah - my last comment was written as the link above was being posted - they crossed. i'm checking the link now. thanks.

In that link I'd be especially sure to try a few different value for the log buffer setting to 9000 if its lower now and to lower if it's higher now.  Setting it lower will be fine if you have adequate disk space at the cost of performance but will reduce memory demand - but its actually more likely to benefit from being set higher especially if you may be short disk space.

You may even need to upgrade the server if it is going to be used in a large commercial setting.

if this caused your problem.

>>I did muck about with registration of sqlvdi.dll about a week ago<<

Fresh drive, Fresh OS install and reinstall sharepoint may be required.  Always make a full image backup of your system before you plan to do any mucking.  It can be a bad thing without a backup.

OK as it turns out we don't have that registry key. That link pertains only to Sharepoint Portal Server I think, and we just have Sharepoint Services installed - the default for SBS.

>>You may even need to upgrade the server if it is going to be used in a large commercial setting.

That's the thing - this is a small company - less than 25 users. we have more than enough disk space, and the processors (2x xeon 2.8GHz) are never taxed.

More than enough disk space may still not be more than enough contiguous disk space.  Did you try the defrag, increased static virtual memory page file and adjusted log buffer settings?

Make SURE all of these machines have been windowsupdate.com patched too IIS is running which makes the machine likely outgoing and therefore a target to intrusion symptoms.

Thanks for the explanation SBS = Small Business Server.   Now I understand.

SBS or not, Exchange and SQL Server don't live together well although, for the small organisation that you described, I think you might just be able to survive with a bit of tweaking.    Memory is the likely bottleneck here.    I don't know of a way to throttle back Exchange memory requirements but, as I described, you can certainly throttle back SQL Server's max memory setting through SQL Server client tools - once you have these installed (no cost).   A RAM upgrade might be in order though.

AustinSeven

Thanks to all of you for promt and considered advice. The key here for me was that, similar to store.exe. sqlserver.exe relinquishes RAM before paging occurs. The info on Enterprise Manager, and where to get it were also important, so that I can manage this in the future. So I split the points.

While we are sharing knowledge I'd also like to share this excellent admin tool I just discovered during my EE browsing today which I think everyone who does "back end" server room work of any kind will appreciate.

http://www.nu2.nu/pebuilder/

These boot CD's are catching on quite a bit they have some that just boot up to tools for partitioning and formatting drives and scanning for viruses etc, but this one is for building an actual full trimmed down Windows XP/2003 boot CD which can be a real life saver too if you ever need to Oh say move the SQL MDF files because of some sort of serious problem/infection/drive sector failure which maybe only affected the OS files and not the MDF.

When supporting an SBS Server, be careful, they are not like regular servers.  I know this post is very old but for those searching, check Susan Bradley's blog www.sbsdiva.com -- her archive article answers this question:  http://msmvps.com/blogs/bradley/archive/2005/05/22/48500.aspx.  It ususally is the sbsmonitoring that is running high memory and is easy to throttle that instance.