Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
ranvir_2k
Posting Yak Master
180 Posts |
Posted - 2013-12-30 : 05:29:25
|
I'm having some performance issues on my SQL Server.In perf mon I can see that Page Faults/sec is constantly at 100.This is on SQL Server 2000, Windows Server 2003.The server has 2GB memory and all of it has been assigned to SQL Server. Should I reduce the memory assigned to SQL Server?Any other advice?Thanks |
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2013-12-30 : 08:51:00
|
According to Technetquote: . This counter gives a general idea of how many times information being requested is not where the application (and VMM) expects it to be. The information must either be retrieved from another location in memory or from the pagefile. Recall that while a sustained value may indicate trouble here, you should be more concerned with hard page faults that represent actual reads or writes to the disk. Remember that the disk access is much slower than RAM.
I wouldn't that concerned about just 100 page faults per sec. Microsoft SQL Server MVP, MCT, MCSE, MCSA, MCP, MCITP, MCTS, MCDBA |
|
|
ranvir_2k
Posting Yak Master
180 Posts |
Posted - 2013-12-30 : 09:09:13
|
No I mean it is at the max value, 100% not 100 page faults/sec. |
|
|
ranvir_2k
Posting Yak Master
180 Posts |
Posted - 2013-12-31 : 06:13:36
|
The average value is 24,000 page faults/sec.Is that an excessive number?Are there any other counters I should monitor at the same time? |
|
|
|
|
|