Most memory allocations that are attributed to the SQL Server process space are controlled through interfaces that allow for tracking and accounting of those allocations. However, memory allocations might be performed in the SQL Server address space that bypasses internal memory management routines. Values are obtained through calls to the base operating system. They are not manipulated by methods internal to SQL Server, except when it adjusts for locked or large page allocations.
All returned values that indicate memory sizes are shown in kilobytes (KB). The column total_virtual_address_space_reserved_kb is a duplicate of virtual_memory_in_bytes from sys.dm_os_sys_info.
The following table provides a complete picture of the process address space.
Process working set in KB, as reported by operating system, plus tracked allocations done by using large page and AWE APIs.
Physical memory that is allocated by using large page APIs.
Physical memory that is allocated by using AWE APIs.
Ttotal size of the user mode part of the virtual address space.
Number of virtual address reservations that is neither committed nor mapped physical pages.
Amount of virtual address that has been committed or mapped to physical pages.
Amount of virtual address space that is currently free.
Number of page faults that are incurred by the SQL Server process.
Percentage of committed memory that is in the working set.
Amount of memory that is available to be committed by the process.
Process is responding to low physical memory notification.
Low virtual memory condition has been detected.