Re: AWE Memory

Any app can use up to 2GB of memory by default. Lock Pages is mainly for memory above 4GB.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Leila" <Leilas@xxxxxxxxxx> wrote in message news:efg4Kt6AIHA.464@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,
Today I was working on a server and I noticed that it's processor is 64 bit while the OS is Windows 2003 32 bit.
The PAE switch was added to boot.ini, AWE option was enabled for SQL Server but the service account was not granted the permission of Lock Page in gpedit.msc.
Performance monitor indicated that SQL Server is using 5.1GB memory out of total 6GB.
My question is that how SQL Server was using 5.1GB of memory while it didn't have Lock Page permission.
Thanks in advance,
Leila


.

Relevant Pages

  • Re: Locking pages in memory
    ... So I think the 64-bit Standard does not support locked pages in memory. ... Rick Byham, SQL Server Books Online ...
    (microsoft.public.sqlserver.setup)
  • Re: Locking pages in memory
    ... the account SQL runs under) the permission to lock pages in memory. ... Server Standard, Enterprise, and Developer editions: Required for SQL Server ...
    (microsoft.public.sqlserver.setup)
  • Re: Locking pages in memory
    ... I have confirmed that SQL Server Standard 64-bit does not use locked pages in memory, even if available in the OS. ... There are some complex reasons behind this, but basically, if you are running on 64-bit Windows, you probably don't need to lock pages in memory. ...
    (microsoft.public.sqlserver.setup)
  • Re: Worker Threads
    ... In order to use more than 4GB of memory you must use AWE. ... One is you must have Enterprise Edition of SQL ... set in the Boot.ini and AWE enabled in SQL Server. ...
    (microsoft.public.sqlserver.setup)
  • Re: AWE settings.
    ... dynamic AWE to work using SQL 2005, but don't quote me on that. ... Microsoft SQL Server MVP ... immediately allocates memory at system startup. ...
    (microsoft.public.sqlserver.setup)