October 23, 2011 at 4:53 pm
I'm getting this message on some of my newly built SQL 2008 R2 servers and I'm just wondering, is it a good idea to grant this permission or not?
I understand from reading I've done that it isn't mandatory, and that it just stops the SQL Server assigned memory from being trimmed.
October 24, 2011 at 6:57 am
It's a complex and often debated topic. This is a pretty good discussion of the issue imo: http://sqlserverperformance.wordpress.com/2011/02/14/sql-server-and-the-lock-pages-in-memory-right-in-windows-server/
October 24, 2011 at 7:09 am
PhilipC (10/23/2011)
I'm getting this message on some of my newly built SQL 2008 R2 servers and I'm just wondering, is it a good idea to grant this permission or not?I understand from reading I've done that it isn't mandatory, and that it just stops the SQL Server assigned memory from being trimmed.
How much memory does the server have?
What steps have you taken to enable Locked Pages?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 25, 2011 at 3:31 pm
Thanks for the link, that's really useful. Appreciate that.
October 26, 2011 at 2:26 am
For whats its worth, I still enable this setting.
This article from the SQLCAT team recommends this as part of their benchmarking.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply