SQL Server misunderstanding 30th on the 5th day AWE must be turned on in 64-bit SQL Server _mssql

Myth #5: AWE must be turned on in 64-bit SQL Server

Error!

The various versions of the set of awe that have been circulated are confusing. For example, how settings work, how settings don't work, whether you need awe on 32-bit and 64-bit.

Well, let me summarize:

• In a 64-bit system (SQL SERVER 2005+ version)
  • AWE is not needed (even on state, it has no effect)
  • Turn on the lock memory page so that the memory pages in the buffer pool are not replaced in virtual memory (virtually all single Page allocator allocations and stolen memory are not replaced)
  • When the lock memory page is turned on, SQL Server allocates memory using the Windows AWE API, which is slightly faster
  • "Lock memory Pages" exist only in standard and Enterprise Editions (the development version of the non production environment is also present)
• In a 32-bit system (SQL SERVER 2005+ version)
  • In order to use more than 4G of memory, awe must be turned on to use additional virtual address space
  • In order to use AWE, the lock memory page permission must be turned on
  • "Lock memory Pages" exist only in standard and Enterprise Editions (the development version of the non production environment is also present)

It looks a bit complicated, and that's why it's confusing.

One of my best friends from CSS, Bob Ward, has a very good blog post: Fun with Locked Pages, AWE, Task Manager, and the Working Set ...

PS: The translator has an article on memory management: Talking about SQL Server management of memory