Lock pages in memory greyed out
in [Server Configuration]
|
Prev: Lock pages in memory greyed out
Next: How to find out the point time when the database is damaged/crashe
From: Jason Woodbury on 3 May 2010 16:40 I have a server running 64bit SQl 2008 standard and the application we have to run on it needs to be able to lock pages in memory. I tried to do this via the local policies but the add users is greyed out and I'm stuck. Currently without that setting i'm using 11.8Gb of memory of the 12 and i'm told this is needed in order to stop that from happening. If someone might know of a way to add the users to this "lock pages in memory" i'd greatly appreciate it. Thanks in advance, Jason
From: Erland Sommarskog on 3 May 2010 17:36 Jason Woodbury (JasonWoodbury(a)discussions.microsoft.com) writes: > I have a server running 64bit SQl 2008 standard and the application we > have to run on it needs to be able to lock pages in memory. I tried to > do this via the local policies but the add users is greyed out and I'm > stuck. Currently without that setting i'm using 11.8Gb of memory of the > 12 and i'm told this is needed in order to stop that from happening. If > someone might know of a way to add the users to this "lock pages in > memory" i'd greatly appreciate it. A couple of this here: o You need some CU of SQL 2008 SP1 to take benefit of Lock Pages in Memory on Standard Edition. o The point with lock pages, is that it prevents SQL Server from losing memory just because a driver goes bezerk. If SQL Server uses 11.8 GB of memory of 12 GB total, something is strange, but then you should set max memory for SQL server. o As for the question, that is about setting a permission in Windows, and it may be best asked in a Windows forum. (It's beyond my area, anyway.) -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
From: TheSQLGuru on 3 May 2010 18:48 lockpages is NOT required to stop SQL Server from taking too much memory, and in fact if you have in on and sql DOES take too much memory it might be less than optimal. Just set your max server memory setting to about 8-9GB and then monitor for paging and other indications of memory pressure. -- Kevin G. Boles Indicium Resources, Inc. SQL Server MVP kgboles a earthlink dt net "Jason Woodbury" <JasonWoodbury(a)discussions.microsoft.com> wrote in message news:008C7B02-CEC9-4BA1-BE87-C3FECF858E8E(a)microsoft.com... >I have a server running 64bit SQl 2008 standard and the application we have > to run on it needs to be able to lock pages in memory. I tried to do this > via the local policies but the add users is greyed out and I'm stuck. > Currently without that setting i'm using 11.8Gb of memory of the 12 and > i'm > told this is needed in order to stop that from happening. If someone > might > know of a way to add the users to this "lock pages in memory" i'd greatly > appreciate it. > > Thanks in advance, > Jason
From: mamalatek on 4 May 2010 14:00
Check to see what group policy is being applied. Jason Woodbury wrote: >I am trying to give the ability to a user to "Lock pages in memory" via local >policy, and for some reason it's greyed out. I can't change this and it is >needed on a version of our software running on SQL standard 2008 64. I've >tried all of the ways listed on the internet but it's continued to be greyed >out. Any info on how to get this to allow for a user to be placed there to >do what I need done would be appreciated. > >Thank you in advance, >Jason |