SQL Server misunderstanding: 5th-day AWE must be enabled in 64-bit SQL SERVER

Misunderstanding #5: AWE must be enabled in 64-bit SQL SERVER

Error!

The various versions related to AWE settings that have been circulated in the workshop are confusing. For example, how to set the function, how to set the function does not work, and whether AWE is required on 32-bit and 64-bit.

Well, let me summarize:

• In a 64-bit System (SQL SERVER 2005 +)
  • AWE is not required (even the ON status has no impact)
  • Enable "lock Memory Page" so that the memory Page in the buffer pool will not be replaced with the virtual memory (in fact, all Single Page Allocator allocation and Stolen memory will not be replaced)
  • When "lock Memory Page" is enabled, SQL Server uses Windows AWE API to allocate memory, which is a little faster
  • The "lock Memory Page" only exists in the standard and enterprise editions)
• In a 32-bit System (SQL SERVER 2005 +)
  • To use memory larger than 4 GB, AWE must be enabled to use additional virtual address space.
  • To use AWE, the "Lock Memory Page" permission must be enabled
  • The "lock Memory Page" only exists in the standard and enterprise editions)

It looks a little complicated. That's why it is confusing.

Bob Ward, a good friend of mine from CSS, has a very good blog post about this: Fun with Locked Pages, AWE, Task Manager, and the Working Set...

PS: the translator has an article on Memory Management: A Discussion on memory management by SQL Server