Carve out in SQL to start at 12GB and max out at 14GB. Then set your locked pages policy to the account SQL is running under. Make sure to put a check in the check box Use AWE to allocate memory in the "Memory" page and in the "Processors" page put a check box in the "Boost SQL Server priority".

In some cases you may need to use the /PAE in the boot.ini. They say it's not needed but I found in some cases, even on Ent version SQL won't address upper memory.

Remember, you can't see the memory usage in "Task Manager". If you really want to see the memory SQL is using run this...

SELECT

--Amount of physical memory on server

physical_memory_in_bytes

, physical_memory_in_bytes / 1024 / 1024.00 as physical_memory_in_MB

,virtual_memory_in_bytes

, virtual_memory_in_bytes / 1024 / 1024.00 as virtual_memory_in_MB

--Committed physical memory in buffer pool

--Does not include MemToLeave memory area

,bpool_committed AS 'Number of 8KB buffers in buffer pool'

, bpool_committed * 8 / 1024.00 as bpool_committed_in_MB

, bpool_commit_target AS 'Number of 8KB buffers needed by the buffer pool'

, bpool_commit_target * 8 / 1024.00 as bpool_commit_target_in_MB

,CASE

WHEN bpool_commit_target > bpool_committed THEN 'Extra memory needed from OS for Buffer Pool'

WHEN bpool_commit_target < bpool_committed THEN 'Memory may be released from Buffer Pool to OS'

END AS 'Status of Dynamic Memory'

, bpool_visible AS 'Number of 8KB Buffers in Buffer Pool that are directly accessible in the processes VAS.'

, bpool_visible * 8 / 1024.00 as bpool_directly_accessible_VAS_in_MB

FROM sys.dm_os_sys_info