As a trial run for a client I am trying to enable the "Lock Pages in Memory" setting on my development server, but no matter what I change, I cannot get the "Using locked pages for buffer pool" to show up in the SQL Server log. I want to make sure I can do this correctly before I do it for a client.
Our development server is a Windows 2003 with 4 GB of RAM, SQL Server 2008 R2 Standard Edition 32Bit.
Below is what I have attempted:
Checked "Use AWE to allocate memory".
Set the "Maximum server memory" setting.
Added startup parameter -T845 in the SQL Server service configuration.
The SQL Server service is running on the LocalSystem Account so from what I have read I do not need to enter an account in the "Lock Pages in Memory" priveledge. However, I did try changing the service to operate under the "Administrator" login, and added that login to the "Lock Pages in Memory" privelege.
Restarted SQL Server Service.
Nothing I have done will put
Using locked pages for buffer pool
into my SQL Server log, but the 845 trace appears to be turned on when I run DBCC TRACESTATUS.
Anyone have any ideas about why nothing I have done appears to turn this on?