October 26, 2010 at 7:05 am
I'm trying to determine how much memory SQL is actually using and not just allocated. I'm using SQL 2005 x64 with 16GB. I first allocated 10GB and it used all 10GB. If I allocated 12GB it's using 12GB. I know this because if I look in perfmon and counters Total Server Memory and Target Server Memory ,they are both showing the same which is roughly 12GB. I've been told that if I allocated 16GB(if I had it), then SQL will use it. So basically, what ever I allocate, SQL will take it? How do I know if I have enough? We are experiencing performance issues and the one question is " how much memory is SQl actually using?" I expect that if I allocate 12GB and SQL only is using 8GB, then that would reflect in the counters...but it doesn't. Thoughts?
October 26, 2010 at 7:52 am
Memory pressure in SQL can best be measured by using Performance Monitor or any of a variety of third party tools.
Start with this: http://msdn.microsoft.com/en-us/library/aa905152(SQL.80).aspx
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
October 26, 2010 at 7:59 am
SQL will always behave this way. The better way to see memory usage it to see if it is 'actually' being used. look at the counter "Buffer cache hit ratio" instead. if your ratio is in the high 99%, then you can start to scale back the memory and use in other instances if you want.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply