Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have an SBS server running SQL Server 2005 and Exchange, that is notoriously tight on memory. (It's a battle between the sql and exchange).

It's not the time yet to replace it completely, but I wonder if stocking up to 8GB (the maximum the board supports, it currently holds 4GB) would help.

Since it's a 32 bit OS, the additional memory would be visible through AWE only, which at least SQL Server seems to support.

  • Can I expect improvements?
  • What config changes (Windows, SQL Server) are necessary so it makes use of AWE?
  • Can Exchange benefit from the additional memory, too?
share|improve this question
add comment

2 Answers

up vote 3 down vote accepted

SBS 2003 will only see 4GB of physical memory so AWE isn't going to do anything for you. Have a look at Memory Limits for Windows Releases.

share|improve this answer
    
Damn, you, sales department! :D - and thanks for the quick answer –  peterchen Jul 28 '09 at 16:19
    
I believe these limits are much more rational in the 2008 editions.. for now, anyway.. –  Jeff Atwood Jul 28 '09 at 22:56
add comment

Small Business Servers nearly always use all the available memory, by design. Both Exchange and SQL Server (by default) will try to use all the available memory, but will release it 'on demand'. Result: your memory is always going to be full.

That's not the same thing as not having enough memory, that is just the server applications using the available resources to maximum effect. Unused memory is wasted memory.

The fact that SQL (by default) uses all available memory can cause problems, particularly the SBSMONITORING instance, which on some systems can begin to consume and unreasonable amount of memory (more then 100 Mb or so is unreasonable). If that's happening on your system then consider limiting the memory available to that instance. These steps in a command prompt will do it:

> osql -E -S YOURSERVERNAME\sbsmonitoring
> sp_configure 'show advanced options',1
> reconfigure with override
> go
> sp_configure 'max server memory', 70    
> reconfigure with override
> go

alt text
(image courtesy of Susan Bradley)

That limits the memory to 70 Mb for the SBSMONITORING instance (70 Mb is a value that has been suggested within the SBS MVP community, your mileage may vary). If you are running SBS Premium and have ISA Server, then you might also need to throttle the ISA logging database using the same technique. In this case, the instance name is MSFW and I have found that 70 Mb works for that, too.

Don't try to limit the Sharepoint instance, though. That should be left on its default settings.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.