Funny you should mention the Private Bytes because that's where I get confused. For example, Task manager may show that sqlservr.exe has 445MB of memory, yet Performance Monitor Private Bytes will show a higher number like 463MB+. And the private bytes fluctuates a little but not much. Is that significant?
And virtual bytes is at 970MB+ yet our page file is only 776MB...Not sure what that's trying to tell me...???
And I understand about SQL holding on to the memory until another process needs it, and maybe another process never needs any more...maybe it's all SQL activity....
....But the bottom line is that it seems contradictory for the cache hit ratio's to be 98%+, and SQL Server:Memory Manager:'Total server memory' to be 134MB, yet Memory
ages/sec to be very active...it's like SQL has plenty of memory and it's finding pages it needs in memory, yet it's writing things in and out of disk (the paging file) like crazy.
Maybe my confusion is that cache hit ratio includes pages "found" in virtual memory (i.e., the paging file)? Is that the case? I guess that would explain why cache hit ratio is high yet pages/sec is also high...does that sound right? And if that's the case, maybe we just need more RAM so it can get the hits in RAM instead of going out to the paging file???