The background: One of our most important production servers runs a SQL database (about 5Gb in size with ~100Gb of flat files). It hosts the server for a program most of our employees use, access is through HTTPS.
It was operating on Windows Server 2003 (32-bit) with 4Gb of RAM and a 4 core non-HT Xeon. SQL was 2005 Workgroup. The hardware was about out of warranty so we recently updated it to a shiny new server sporting a 6 core HT enabled Xeon with 12Gb of RAM. It now on Windows Server 2008 R2 and SQL 2008 R2 Workgroup.
The system never really used a lot of the CPU, even on the old hardware. Now it barely scratches the surface. It has doubled the amount of RAM it uses though, we always knew the 4Gb was holding it back.
My question stems from this: perfmon report
This was over 4 hours, covering the busiest and quietest parts of the work day around here. (including some scheduled reports)
Note the Pages/Sec averages 52. Most sources I have read say anything over 20/sec indicates a memory issue. The server had between 7.2 and 7.8Gb of RAM in use throughout the test, so 4Gb+ free at all times.
What I am wondering is, should I be concerned here. I think it is the nature of the SQL database and the program it supports that causes the high paging, not a lot of duplicate hits. Can anyone back this theory up? Or, is the server in need of more RAM as other sources have suggested?
In case it matters C: & E: are partitions on a RAID 1 array of 7.2k disks, D: is a RAID 1 of 15k disks.
[link] [2 comments]