SELECT
SUM( multi_pages_kb +
virtual_memory_committed_kb +
shared_memory_committed_kb +
awe_allocated_kb ) AS [Used by BPool, KB]
FROM
sys.dm_os_memory_clerks
WHERE
[type] = 'MEMORYCLERK_SQLBUFFERPOOL'

Buffer Counts Buffers
------------------------------ --------------------
Committed 786432
Target 786432
Hashed 722004
Stolen Potential 127447
External Reservation 0
Min Free 128
Visible 195584
Available Paging File 401426

Procedure Cache Value
------------------------------ -----------
TotalProcs 6878
TotalPages 54239
InUsePages 105

Steve Jones - Editor (5/27/2008)

---

Tend to agree with Michael. Monitor and observe the system. AWE isn't needed for 64-bit and my guess is SQL will keep building cache and run to 30GB unless you limit it.

Wilfred van Dijk (5/27/2008)

---

You need AWE to prevent memory stealing by the OS.
Also make sure you have a minimum and maximum size. Don't set the maximum size to unlimited, or SQL will compete with your OS for the last MBs.
We have the same configuration and our max memorysize is 28GB (min size is 16GB)

Also, be aware of memory trashing if you do a large OS filecopy on that server.
You also get memory messages in your logfile when adding/deleting databases/snapshots, but these are ok.