Hi, we are currently running Exchange 2007 on a Dell server T610(16gbRAM), Windows SBS 2008.
Up until a couple of weeks ago Exchange was running fine and all the 40 odd users were happy.
Now we seem to be having performance issues when users are accessing the Public Folders in Exchange, users are not finding it easy to scroll through Public Folders without there screen freezing when scrolling and opening emails.
There is plenty of room on the server and Public Folders are appox. 60GB.
I have been looking around to try and find the answer and have been looking at the Exchange Performance Monitor but do not know how to interpret the tools as I am a complete novice.
I have run Best Practice Analyser tool from the Toolbox in EMC and got the following results:
1. Organisation incoming message size too high - The maximum incoming message size is set too high. This can cause reliability problems. Current maximum message size is 39.0625 MB.
2. Organisation outgoing message size too high - The maximum outgoing message size is set too high. This can cause reliability problems. Current maximum message size is 39.0625 MB
3. The database cache size is not set to the recommended value
Our database cache is set to: 134,217,728
Recommended cache: 536,870,912
The incoming/outgoing messages are high as we do get the odd very large message in/out but not many.
The database cache is something I know nothing about, is this something we should change and if so could anyone give me a steer on a couple of things:
- Is it limited to this public folder storage file or is it across all exchange?
- Is the effect immediate or do I need to wait / reboot / restart certain services (guess the next question).
- How can I check it isn't going to bring the server to its knees?
○ I open up Taskmgr, show processes from all users and it says Physical Memory 91%, but maybe that is just processes using up the available.
○ Should I be looking at the "Memory (Private working….),
○ Sqlserv.exe = 4.9GB, sqlserv.exe*32 = 1.4GB, store.exe 631MB.
○ I am assuming the sqlserv is something to do with exchange as we don't run anything on it and don't use sharepoint (although it could well be running)
Additional Info:
Disks: c = OS = 134GB of which there is 13GB free - we manage this to always be > 10GB (mirror)
D = 890GB of which 200GB is free
Any help gratefully received or questions / suggestions that we can work through to isolate the problem without killing the server.
