SQL Server 2012 64-bit use AWE API for LPIM. Even AWE is no longer needed on the 64-bit because the VAS on the 64-bit is significant larger ( 8TB), however, SQL server engineer found to use the AWE API for LPIM could get the performance gain for SQL server memory allocation. ( http://blogs.msdn.com/b/slavao/archive/2005/04/29/413425.aspx) .
When AWE enable ( in any version) , the memory that is allocated through AWE API would not be part of the working set memory hence, it is “LOCK” . This is the reason that LPIM privilege needs to be set on the SQL server account.
Grant the LPIM privilege
Add the SQL server account to the Lock Page in memory policy through gpedit.msc.
SQL Server error log
VMMAP would also show the locked Working set. the number is the same as the result we see in the DMV.
No More AWE in SQL 2012
Here is the screenshot from SQL Server 2012 from SSMS.
Here is the screenshot from SQL Server 2008R2 from SSMS