August 18, 2010 at 10:02 pm
My configuration : SQL Server 2005 x64 Standard Edition, MS clustering,
version : 9.0.4226
I enabled the SMO and DMO extended stored procedures.
I used gpedit.msc to add the account that runs the SQL Server Service and re-started the service.
But from the ERRORLOG file, I couldn't find the statement : Using locked pages for buffer pool.
Are there some things I missed ?
Or does SQL Server 2005 x64 Standard Edition + sp3 + cu4 really support Lock Page ?
August 19, 2010 at 4:54 am
Have you added the SQL service account to have access to the policy?
August 19, 2010 at 9:13 am
Quick way to check if it's enabled is try enabling AWE on the server.
Run it via t-sql with sp_configure:
sp_configure 'awe enabled',1
reconfigure
If it lets you, then the policy is set correctly. If it's not set correctly, you will get an error saying the Lock Pages In Memory permission is not set (or something along those lines).
August 19, 2010 at 11:58 am
onlo (8/18/2010)
and re-started the service.
you have to reboot the server, this is an operating system policy which will be forced by a reboot. Service restart has no effect!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 19, 2010 at 3:50 pm
You need to add trace flag 845 as a startup trace flag in order to use lock pages in memory for SQL 2005 Standard.
August 23, 2010 at 7:51 pm
Yes, I got it.
I forgot to add the Trace Flag.
Once I added it and restarted the SQL Service, I could see the message : Using locked pages for buffer pool.
Thanks every bodies.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply