Allocations that are internal to SQL Server use the SQL Server memory manager. Tracking the difference between process memory counters from sys.dm_os_process_memory and internal counters can indicate memory use from external components in the SQL Server memory space.
Memory brokers fairly distribute memory allocations between various components within SQL Server, based on current and projected usage. Memory brokers do not perform allocations. They only track allocations for computing distribution.
The following table provides information about memory brokers.
Type of memory broker. There are currently three types of memory brokers in SQL Server.
MEMORYBROKER_FOR_CACHEMemory that is allocated for use by cached objects.
MEMORYBROKER_FOR_STEALMemory that is stolen from the buffer pool. This memory is not available for reuse by other components until it is freed by the current owner.
MEMORYBROKER_FOR_RESERVEMemory reserved for future use by currently executing requests.
Amount of memory, in kilobytes (KB), that has been allocated to this type of broker.
Current rate of allocation that is attributed to this broker.
Recommended amount of allocated memory, in kilobytes (KB), that is based on current settings and the memory usage pattern. This broker should grow to or shrink to this number.
Projected number of allocations, in kilobytes (KB), that will be done in the next several seconds.
Memory usage recommendation that is based on the current settings and usage pattern. Valid values are as follows:
ID of the resource pool if it is associated with a Resource Governor pool.
Rate of memory allocations in kilobytes (KB) per second. This value can be negative for memory deallocations.
Predicted amount of allocated memory by the broker. This is based on the memory usage pattern.
Maximum amount of memory, in kilobytes (KB), that the the broker can allocate.