Winfried Terlinden (2/28/2012)
This privilege must be enabled to configure Address Windowing Extensions (AWE). (...) On 32-bit operating systems, setting this privilege when not using AWE can significantly impair system performance. Locking pages in memory is not required on 64-bit operating systems.
Hi Winfried.
First of all, yes Lock Pages in Memory may cause issues on 32-bit systems without AWE. As I understand this issue, this is mainly since SQL Server will use and lock as much memory as it can in the first 4GB. With AWE enabled, this memory may be allocated above 4GB, which is less likely to affect other programs. Some have experienced similar issues with Lock Pages in Memory on 64-bit systems if Max Server Memory is not configured.
Lock pages in Memory is not required for allowing 32-bit applications (as SQL Server x86 Editions) to allocate memory above 4GB. It is still required for preventing the OS from paging the buffer pool however.