July 19, 2010 at 4:13 am
Further to req. by app guy, I set lock pages in memory for sql server user, restarted sql, set max mem on server = 15gb, ticked awe & restarted.
Previously sql consumed more & more memory up to 28gb of the avail 33 gb on server (when looking in task manager). Now it just sits at 113 mb. Why is this? I want to be able to explain why to the app guys. Is it just that the server hasn't needed more yet?
How can I load the server / make it need more memory so I can test it.
How can I see how much memory is actually being used by the server?
2005, 64 bit, ent.
Would really appreciate advice as always!!
July 19, 2010 at 4:34 am
You're looking in Task Manager for the memory usage, yes?
Locked pages aren't part of the process' working set and so aren't visible there.
Use the SQL Server performance monitor counters instead.
The (fascinating) details for why this is can be found here:
By the way, 'ticking AWE' is not required on 64 bit SQL Server (it doesn't do anything, so it doesn't do any harm either).
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
July 19, 2010 at 8:17 am
Thanks hombre. I'll check it out now.
July 19, 2010 at 8:25 am
Hombré? :unsure: :blink: 😎
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
July 19, 2010 at 9:07 am
Sorry I work with lots of mexicans ... I just mean thanks man. 😉
July 19, 2010 at 9:15 am
baby_cheeses (7/19/2010)
Sorry I work with lots of mexicans ... I just mean thanks man. 😉
Sweet as, bro 😀
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply