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.

Hey all, plase bear with me as I haven't looked at a server in a very long time.

The problem I am having is with a Windows 2008 Standard FE Service Pack 2

Intel Xeon X3430 @ 2.40 2.39 GHZ
4 GB Memory
64 Bit

There seems to be no problems other than the physical memory peaking at 91%, always with over 100 Hard Faults Per Second.

To my understanding hard faults should be fairly rare on a machine with.

Are there any logs I can show you? Or investigate myself.

The general performance of the machine is ok, i can access SBS2008 and change settings fairly smoothly without hangs etc. However, we connect to the server and do quite a bit of SQL via an application. For a record to retrieve say 20 rows, it can take 20+ seconds.

Thanks in advance, Jamie

EDIT:

What the server is used for:

  • IIS ASP Web Service
  • SQL 2008
  • List item
  • Exchange

unable to upload screenshots due to low reputation - why doesnt my SO work here :)

enter image description here

enter image description here

share|improve this question
3  
For the record, 4Gb is the bare minimum I would consider running SBS2008 on. We had a server that started with 4Gb, after 3 months we'd gone and bumped it up to 8Gb. 6 Months after that we bumped it up to 16Gb and now it seems happy. –  Mark Henderson Mar 15 '11 at 23:30
    
wow really? i need to kick the tech in the balls! –  claw Mar 15 '11 at 23:46
    
@Claw - well, before going that far, there may be other reasons it's being RAM starved. Budget issues, availability, priorities, etc. –  Mark Henderson Mar 15 '11 at 23:49
    
Please take a screenshot, just like this: stackoverflow.com/questions/2618406/… We need more information on the processes running to see where the memory leak is. Sounds to me like SQL server is being choked. Is this server ONLY SQL server or is there an IIS process running on it? Please clarify the scope of this server. –  IT_Fixr Mar 15 '11 at 23:53
    
@IT+Fixr I have uploaded a few images to IMGUR please see OP edit –  claw Mar 16 '11 at 0:06

1 Answer 1

So without more diag and troubleshooting I would say your best bet is to (at least) double the RAM from 4 to 8GB per Microsoft recommendations, which will allow more room for SQL to store table data in RAM.

You'll notice by your Commit column in the screenshots that the other busy services with lots of RAM activity are Exchange and Exchange Edge Svc (which you may be able to disable that service if you don't have an exch edge server). it also looks like you have two SQL server instances running, which I think is the norm for SBS.

You can look in Performance Monitor for Physical Disk "Avg. Disk Queue Length" which shouldn't be more then 1-2 times the number of physical disks... which if it is will tell you the server needs more disk I/O (more disks) but that could be a red herring, as when you are low on RAM then the server is forced to use more disk in the paging file. Adding RAM will reduce the use of disk as "pretend RAM" and make everything from logons to SQL and Exchange snappier in my experience.

share|improve this answer

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.