SQL Server Performance

AWE - Lock pages in Memory query

Discussion in 'SQL Server 2005 General DBA Questions' started by Trev256b, May 24, 2011.

  1. Trev256b Member

    Why if you enable the 'lock pages in memory' option and don't enable AWE, can you incur a performacne problem? Is this because you might lock too many pages in memory for SQL Server processes which will never be released, and consequenlty there will not be enough memeory for the operating system?
  2. Jahanzaib Member

    AWE not needed in 64-bit version of OS and SQL Server 64-bit edition,In 32-bit version you have to define AWE and lock pages ,if you define lock pages enable for the specific user account and you did not enable AWE then SQL Server will not gain memory

    If you don't enable lock pages for the specific user and anti-virus is running on the OS then OS understand that is a virus and process is going crash or drop
  3. Trev256b Member

    Sorry that doesn't answer the question. Why might you get performance problem when you enable lock pages in memory and dont setup awe?
  4. Jahanzaib Member

    Becuase when SQL Server need more RAM then it cant ,Page life will be suffer and physical IOs increase ,your SQL Server Service account must have lock pages rights on the running OS

Share This Page