Use the DBCC MEMORYSTATUS command to monitor memory usage in SQL Server

Άρθρο
10/09/2023

This article describes how to use the DBCC MEMORYSTATUS command to monitor the memory usage.

Original product version: SQL Server
Original KB number: 907877

Introduction

The DBCC MEMORYSTATUS command provides a snapshot of the current memory status Microsoft SQL Server and the OS. It provides one of the most detailed outputs of memory distribution and usage in SQL Server. You can use the output to troubleshoot memory consumption issues in SQL Server or to troubleshoot specific out-of-memory errors. Many out-of-memory errors automatically generate this output in the error log. If you experience an error that's related to a low-memory condition, you can run the DBCC MEMORYSTATUS command and provide the output when you contact Microsoft Support.

The output of the DBCC MEMORYSTATUS command includes sections for memory management, memory usage, aggregate memory information, buffer pool information, and procedure cache information. It also describes the output of global memory objects, query memory objects, optimization, and memory brokers.

Note

Performance Monitor (PerfMon) and Task Manager don't account for full memory usage if the Locked Pages in Memory option is enabled. There are no performance counters that show Address Windowing Extensions (AWE) API memory usage .

Important

The DBCC MEMORYSTATUS command is intended to be a diagnostic tool for Microsoft Support. The format of the output and the level of detail that's provided are subject to change between service packs and product releases. The functionality that the DBCC MEMORYSTATUS command provides might be replaced by a different mechanism in later product versions. Therefore, in later product versions, this command might no longer function. No additional warnings will be provided before this command is changed or removed. Therefore, applications that use this command might break without warning.

The output of the DBCC MEMORYSTATUS command has changed from earlier releases of SQL Server. Currently, it contains several tables that were unavailable in the earlier product versions.

How to use DBCC MEMORYSTATUS

DBCC MEMORYSTATUS is typically used to investigate low-memory issues that are reported by SQL Server. Low memory can occur if there's either external memory pressure from outside the SQL Server process or internal pressure that originates within the process. Internal pressure might be caused by the SQL Server database engine, or by other components that run within the process (such as linked servers, XPs, SQLCLR, intrusion protection, or anti-virus software). For more information about how to troubleshoot memory pressure, see Troubleshoot out of memory or low memory issues in SQL Server.

Here are the general steps for using the command and interpreting its results. Specific scenarios might require that you approach the output a bit differently, but the overall approach is outlined here.

Run the DBCC MEMORYSTATUS command.
Use the Process/System Counts and Memory Manager sections to establish whether there's external memory pressure (for example, the computer is low on physical or virtual memory, or the SQL Server working set is paged out). Also, use these sections to determine how much memory the SQL Server database engine has allocated in comparison to the overall memory on the system.
If you establish that there's external memory pressure, try to reduce the memory usage by other applications and by the OS, or add more RAM.
If you establish that the SQL Server engine is using most of the memory (internal memory pressure), you can use the remaining sections of DBCC MEMORYSTATUS to identify which components (Memory clerk, Cachestore, UserStore, or Objectstore) are the largest contributor to this memory usage.
Examine each component: MEMORYCLEARK, CACHESTORE, USERSTORE, and OBJECTSTORE. Examine its Pages Allocated value to determine how much memory that component is consuming inside SQL Server. For a brief description of most database engine memory components, see the Memory Clerk types table.
1. In rare cases, the allocation is a direct virtual allocation instead of going through the SQL Server memory manager. In those cases, examine the VM Committed value under the specific component instead of Pages Allocated.
2. If your computer uses NUMA, then some memory components are broken out per node. For example, you can observe OBJECTSTORE_LOCK_MANAGER (node 0), OBJECTSTORE_LOCK_MANAGER (node 1), OBJECTSTORE_LOCK_MANAGER (node 2), and so on, and finally observe a summed value of each node in OBJECTSTORE_LOCK_MANAGER (Total). The best place to start is at the section that reports the total value, and then examine the breakdown, as necessary. For more information, see Memory usage with NUMA nodes.
Some sections of DBCC MEMORYSTATUS provide detailed and specialized information about particular memory allocators. You can use those sections to understand additional details and see a further breakdown of the allocations within a memory clerk. Examples of such sections include Buffer Pool (data and index cache), Procedure cache/plan cache, Query Memory Objects (memory grants), Optimization Queue and small, and medium and big gateways (optimizer memory). If you already know that a particular component of memory in SQL Server is the source of memory pressure, you might prefer to go directly to that specific section. For example, if you have established in some other way that there's a high usage of memory grants that causes memory errors, you can review the Query memory objects section.

The remainder of this article describes some of the useful counters in the DBCC MEMORYSTATUS output that can enable you to diagnose memory issues more effectively.

Process/System Counts

This section provides a sample output in a tabular format and describes its values.

Process/System Counts                Value
------------------------------------ ------------
Available Physical Memory            5060247552
Available Virtual Memory             140710048014336
Available Paging File                7066804224
Working Set                          430026752
Percent of Committed Memory in WS    100
Page Faults                          151138
System physical memory high          1
System physical memory low           0
Process physical memory low          0
Process virtual memory low           0

The following list discusses values and their descriptions:

Available Physical Memory: This value shows the overall amount of free memory on the computer. In the example, the free memory is 5,060,247,552 bytes.
Available Virtual Memory: This value shows the overall amount of free virtual memory for SQL Server process is 140,710,048,014,336 bytes (128 TB). For more information, see Memory and Address Space Limits.
Available Paging File: This value shows the free paging file space. In the example, the value is 7,066,804,224 bytes.
Working Set: This value shows the overall amount of virtual memory that the SQL Server process has in RAM (isn't paged out) is 430,026,752 bytes.
Percent of Committed Memory in WS: This value shows what percent of SQL Server allocated virtual memory is resides in in RAM (or is Working Set). The value of 100 percent shows that all of the committed memory is stored in RAM and 0 percent of it is paged out.
Page Faults: This value shows the overall amount of hard and soft page faults for the SQL Server. In the example, the value is 151,138.

The remaining four values are binary or boolean.

System physical memory high value of 1 indicates that SQL Server considers the available physical memory on the computer is high. That's why the value of System physical memory low is 0, which means no low memory. Similar logic is applied to Process physical memory low and Process virtual memory low, where 0 means it's false, and 1 means it's true. In this example, both values are 0, which means there's plenty of physical and virtual memory for the SQL Server process.

Memory Manager

This section provides a sample output of the Memory Manager that shows the overall memory consumption by SQL Server.

Memory Manager             KB
-------------------------- --------------------
VM Reserved                36228032
VM Committed               326188
Locked Pages Allocated     0
Large Pages Allocated      0
Emergency Memory           1024
Emergency Memory In Use    16
Target Committed           14210416
Current Committed          326192
Pages Allocated            161904
Pages Reserved             0
Pages Free                 5056
Pages In Use               286928
Page Alloc Potential       15650992
NUMA Growth Phase          0
Last OOM Factor            0
Last OS Error              0

The following list discusses values in the output and their descriptions:

VM Reserved: This value shows the overall amount of virtual address space (VAS) or virtual memory (VM) that SQL Server has reserved. Virtual memory reservation doesn't actually use physical memory; it simply means that virtual addresses are set aside from within the large VAS. For more information, see VirtualAlloc(), MEM_RESERVE.
VM Committed: This value shows the overall amount of virtual memory (VM) that SQL Server has committed (in KB). This means that memory used by the process is backed by physical memory or less frequently by page file. The previously reserved memory addresses are now backed by a physical storage; that is they're allocated. If Locked Pages in Memory is enabled, SQL Server uses an alternative method to allocate memory, AWE API and most the memory isn't reflected in this counter. See [Locked Pages Allocated](#Locked Pages Allocated) for those allocations. For more information, see VirtualAlloc(), MEM_COMMIT.
Pages Allocated: This value shows the total number of memory pages that are allocated by SQL Server database engine.
Locked Pages Allocated: This value represents the amount of memory, in kilobytes (KB), that SQL Server has allocated and locked in physical RAM using the AWE API. It indicates how much memory SQL Server is actively using and has requested to be kept in memory to optimize performance. By locking pages in memory, SQL Server ensures that critical database pages are readily available and not swapped to disk. For more information, see Address Windows Extensions (AWE) memory. A value of zero indicates that the "locked pages in memory" feature is currently disabled and SQL Server uses virtual memory instead. In such a case the VM Committed value would represent the memory allocated to SQL Server.
Large Pages Allocated: This value represents the amount of memory allocated by SQL Server using Large Pages. Large Pages is a memory management feature provided by the operating system. Instead of using the standard page size (typically 4 KB), this feature uses a larger page size, such as 2 MB or 4 MB. A value of zero indicates that the feature isn't enabled. For more information, see Virtual Alloc(), MEM_LARGE_PAGES.
Target Committed: This value indicates the target amount of memory that SQL Server aims to have committed, an ideal amount of memory SQL Server could consume, based on recent workload.
Current Committed: This value indicates the amount of the operating system's memory (in KB) the SQL Server memory manager has currently committed (allocated in physical store). This value includes either "locked pages in memory" (AWE API) or virtual memory. Therefore, this value is close to or the same as VM Committed or Locked Pages Allocated. Note that when SQL Server uses the AWE API, some memory is still allocated by the OS Virtual Memory Manager and will be reflected as VM Committed.
NUMA Growth Phase: This value indicates whether SQL Server is currently in a NUMA growth phase. For more information about this initial ramp up of memory when NUMA nodes exist on the machine, see How It Works: SQL Server (NUMA Local, Foreign and Away Memory Blocks).
Last OS Error: This value shows the last OS error that occurred when there was a memory pressure on the system. SQL Server records that OS error and shows it in the output. For a full list of OS errors, see System Error Codes.

Memory usage with NUMA nodes

The Memory Manager section is followed by a summary of memory usage for each memory node. In a non-uniform memory access (NUMA) enabled system, there's a corresponding memory node entry for each hardware NUMA node. In an SMP system, there's a single memory node entry. The same pattern is applied to other memory sections.

Memory node Id = 0      KB
----------------------- -----------
VM Reserved             21289792
VM Committed            272808
Locked Pages Allocated  0
Pages Allocated         168904
Pages Free              3040
Target Committed        6664712
Current Committed       272808
Foreign Committed       0
Away Committed          0
Taken Away Committed    0

Note

The Memory node Id value might not correspond to the hardware node ID.
These values show the memory that is allocated by threads that are running on this NUMA node. These values are not the memory that is local to the NUMA node.
The sums of the VM Reserved values and the VM Committed values on all memory nodes will be slightly less than the corresponding values that are reported in the Memory Manager table.
NUMA node 64 (node 64) is reserved for DAC and is rarely of interest in memory investigation because this connection uses limited memory resources. For more information about dedicated administrator connection (DAC), see Diagnostic connection for database administrators.

The following list discusses values in the output table and their descriptions:

VM Reserved: Shows the virtual address space (VAS) that is reserved by threads that are running on this node.
VM Committed: Shows the VAS that is committed by threads that are running on this node.

Aggregate memory

The following table contains aggregate memory information for each clerk type and NUMA node. For a NUMA-enabled system, you might see output that resembles the following:

MEMORYCLERK_SQLGENERAL (node 0) KB
------------------------------  --------------------
VM Reserved                     0
VM Committed                    0
Locked Pages Allocated          0
SM Reserved                     0
SM Commited                     0
Pages Allocated                 5416

MEMORYCLERK_SQLGENERAL (node 1) KB
------------------------------- --------------------
VM Reserved                     0
VM Committed                    0
Locked Pages Allocated          0
SM Reserved                     0
SM Commited                     0
Pages Allocated                 136

MEMORYCLERK_SQLGENERAL (Total)  KB
------------------------------- --------------------
VM Reserved                     0
VM Committed                    0
Locked Pages Allocated          0
SM Reserved                     0
SM Commited                     0
Pages Allocated                 5552

The value of Pages Allocated shows the overall number of memory pages that are allocated to by a specific component (memory clerk, userstore, objectstore or cache store).

Note

These node IDs correspond to the NUMA node configuration of the computer that's running SQL Server. The node IDs include possible software NUMA nodes that are defined on top of hardware NUMA nodes or on top of an SMP system. To find mapping between node IDs and CPUs for each node, see Information Event ID 17152. This event is logged in the Application log in Event Viewer when you start SQL Server.

For an SMP system, you see only one table for each clerk type, not counting node = 64 used by DAC. This table resembles the following example.

MEMORYCLERK_SQLGENERAL (Total)     KB
--------------------------------- --------------------
VM Reserved                        0
VM Committed                       0
AWE Allocated                      0
SM Reserved                        0
SM Commited                        0
Pages Allocated                    2928

Other information in these tables is about shared memory:

SM Reserved: Shows the VAS that's reserved by all clerks of this kind that are using the memory-mapped files API. This API is also known as shared memory.
SM Committed: Shows the VAS that's committed by all clerks of this kind that are using memory-mapped files API.

As an alternative method, you can obtain summary information for each clerk type for all memory nodes by using the sys.dm_os_memory_clerks dynamic management view (DMV). To do this, run the following query:

SELECT
  TYPE,
  SUM(virtual_memory_reserved_kb) AS [VM Reserved],
  SUM(virtual_memory_committed_kb) AS [VM Committed],
  SUM(awe_allocated_kb) AS [AWE Allocated],
  SUM(shared_memory_reserved_kb) AS [SM Reserved],
  SUM(shared_memory_committed_kb) AS [SM Committed],
  -- SUM(multi_pages_kb) AS [MultiPage Allocator],          /*Applies to: SQL Server 2008   (10.0.x) through SQL Server 2008 R2 (10.50.x).*/
  -- SUM(single_pages_kb) AS [SinlgePage Allocator],        /*Applies to: SQL Server 2008   (10.0.x) through SQL Server 2008 R2 (10.50.x).*/
  SUM(pages_kb) AS [Page Allocated]                      /*Applies to: SQL Server 2012 (11.  x) and later.*/
FROM sys.dm_os_memory_clerks
GROUP BY TYPE

Buffer pool details

This is an important section that provides a breakdown of different states data and index pages within the buffer pool, also known as data cache. The following output table lists details about the buffer pool and other information.

Buffer Pool                                       Pages
------------------------------------------------- ---------
Database                                          5404
Simulated                                         0
Target                                            16384000
Dirty                                             298
In IO                                             0
Latched                                           0
IO error                                          125
In Internal Pool                                  0
Page Life Expectancy                              3965

The following list discusses values in the output and their descriptions:

Database: Shows the number of buffers (pages) that have database content (data and index pages).
Target: Shows the target size of the buffer pool (buffer count). See Target Committed memory in the previous sections of this article.
Dirty: Shows the pages that have database content and have been modified. These buffers contain changes that must be flushed to disk typically by the checkpoint process.
In IO: Shows the buffers that are waiting for a pending I/O operation. This means the contents of these pages is either being written to or read from storage.
Latched: Shows the latched buffers. A buffer is latched when a thread is reading or modifying the contents of a page. A buffer is also latched when the page is being read from disk or written to disk. A latch is used to maintain the physical consistency of the data on the page while it's being read or modified. In contrast, a lock is used to maintain logical and transactional consistency.
IO error: Shows the count of buffers that may have encountered any I/O-related OS errors (this doesn't necessarily indicate a problem).
Page Life Expectancy: This counter measures the amount of time in seconds that the oldest page has stayed in the buffer pool.

You can obtain detailed information about buffer pool for database pages by using the sys.dm_os_buffer_descriptors DMV. But use this DMV with caution because it can run a long time and produce a huge output if your SQL Server-based server is allowed to have lots of RAM at its disposal.

Plan cache

This section discusses the plan cache that was previously referred to as a procedure cache.

Procedure Cache         Value
----------------------- -----------
TotalProcs              4
TotalPages              25
InUsePages              0

The following list discusses values in the output and their descriptions:

TotalProcs: This value shows the total cached objects currently in the procedure cache. This value matches the number of entries in the sys.dm_exec_cached_plans DMV.

Note

Because of the dynamic nature of this information, the match might not be exact. You can use PerfMon to monitor the SQL Server: Plan Cache object and the sys.dm_exec_cached_plans DMV for detailed information about the type of cached objects, such as triggers, procedures, and ad hoc objects.
TotalPages: Shows the cumulative pages used to store all the cached objects in the plan or procedure cache. You can multiply this number by 8 KB, to get the value expressed in KBs.
InUsePages: Shows the pages in the procedure cache that belong to procedures that are currently active. These pages can't be discarded.

Global Memory Objects

This section contains information about various global memory objects and the amount of memory that they use.

Global Memory Objects               Buffers
----------------------------------  ----------------
Resource                            576
Locks                               96
XDES                                61
DirtyPageTracking                   52
SETLS                               8
SubpDesc Allocators                 8
SE SchemaManager                    139
SE Column Metadata Cache            159
SE Column Metadata Cache Store      2
SE Column Store Metadata Cache      8
SQLCache                            224
Replication                         2
ServerGlobal                        1509
XP Global                           2
SortTables                          3

The following list discusses values in the output and their descriptions:

Resource: Shows the memory that the Resource object uses. It is used by the storage engine for various server-wide structures.
Locks: Shows the memory used by the Lock Manager.
XDES: Shows the memory used by the Transaction Manager.
SETLS: Shows the memory that is used to allocate the Storage Engine-specific per-thread structure that uses thread local storage (TLS). For more information, see Thread Local Storage.
SubpDesc Allocators: Shows the memory that's used for managing subprocesses for parallel queries, backup operations, restore operations, database operations, file operations, mirroring, and asynchronous cursors. These subprocesses are also known as "parallel processes".
SE SchemaManager: Shows the memory that Schema Manager uses to store Storage Engine-specific metadata.
SQLCache: Shows the memory that's used to save the text of ad hoc and prepared statements.
Replication: Shows the memory that the server uses for internal replication subsystems.
ServerGlobal: Shows the global server memory object that's used generically by several subsystems.
XP Global: Shows the memory used by the extended stored procedures.
SortTables: Shows the memory used by the sort tables.

Query memory objects

This section describes Query Memory grant information. It also includes a snapshot of the query memory usage. Query memory is also known as "workspace memory".

Query Memory Objects (default)           Value
---------------------------------------- -------
Grants                                    0
Waiting                                   0
Available                                 436307
Current Max                               436307
Future Max                                436307
Physical Max                              436307
Next Request                              0
Waiting For                               0
Cost                                      0
Timeout                                   0
Wait Time                                 0

If the size and the cost of a query satisfy "small" query memory thresholds, the query is put in a small query queue. This behavior prevents smaller queries from being delayed behind larger queries that are already in the queue.

The following list discusses values in the output and their descriptions:

Grants: Shows the number of running queries that have memory grants.
Waiting: Shows the number of queries that are waiting to obtain memory grants.
Available: Shows the buffers that are available to queries for use as hash workspace and sort workspace. The Available value is updated periodically.
Next Request: Shows the memory request size, in buffers, for the next waiting query.
Waiting For: Shows the amount of memory that must be available to run the query to which the Next Request value refers. The Waiting For value is the Next Request value multiplied by a headroom factor. This value effectively guarantees that a specific amount of memory will be available when the next waiting query is run.
Cost: Shows the cost of the next waiting query.
Timeout: Shows the time-out, in seconds, for the next waiting query.
Wait Time: Shows the elapsed time, in milliseconds, since the next waiting query was put in the queue.
Current Max: Shows the overall memory limit for query execution. This value is the combined limit for both the large query queue and the small query queue.

For more information about what memory grants are, what these values mean, and how to troubleshoot memory grants, see Troubleshoot slow performance or low memory issues caused by memory grants in SQL Server.

Optimization memory

Queries are submitted to the server for compilation. The compilation process includes parsing, algebraization, and optimization. Queries are classified based on the memory that each query consumes during the compilation process.

Note

This amount doesn't include the memory that's required to run the query.

When a query starts, there's no limit on how many queries can be compiled. As the memory consumption increases and reaches a threshold, the query must pass a gateway to continue. There's a progressively decreasing limit of simultaneously compiled queries after each gateway. The size of each gateway depends on the platform and the load. Gateway sizes are chosen to maximize scalability and throughput.

If the query can't pass a gateway, it waits until memory is available or returns a time-out error (Error 8628). Additionally, the query might not acquire a gateway if you cancel the query or if a deadlock is detected. If the query passes several gateways, it doesn't release the smaller gateways until the compilation process has completed.

This behavior lets only a few memory-intensive compilations occur at the same time. Additionally, this behavior maximizes throughput for smaller queries.

The next table provides details of memory waits that occur because of insufficient memory for query optimization. The internal memory accounts for optimizer memory that's used by system queries, whereas the default reports optimization memory for user or application queries.

Optimization Queue (internal)      Value
---------------------------------- ----------------
Overall Memory                     4013162496
Target Memory                      3673882624
Last Notification                  1
Timeout                            6
Early Termination Factor           5

Small Gateway (internal)           Value
---------------------------------- ----------------
Configured Units                   32
Available Units                    32
Acquires                           0
Waiters                            0
Threshold Factor                   380000
Threshold                          380000

Medium Gateway (internal)          Value
---------------------------------- ----------------
Configured Units                   8
Available Units                    8
Acquires                           0
Waiters                            0
Threshold Factor                   12
Threshold                          -1

Big Gateway (internal)             Value
---------------------------------- ----------------
Configured Units                   1
Available Units                    1
Acquires                           0
Waiters                            0
Threshold Factor                   8
Threshold                          -1

Optimization Queue (default)       Value
---------------------------------- ----------------
Overall Memory                     4013162496
Target Memory                      3542319104
Last Notification                  1
Timeout                            6
Early Termination Factor           5

Small Gateway (default)            Value
---------------------------------- ----------------
Configured Units                   32
Available Units                    32
Acquires                           0
Waiters                            0
Threshold Factor                   380000
Threshold                          380000

Medium Gateway (default)           Value
---------------------------------- ----------------
Configured Units                   8
Available Units                    8
Acquires                           0
Waiters                            2
Threshold Factor                   12
Threshold                          -1

Big Gateway (default)              Value
---------------------------------- ----------------
Configured Units                   1
Available Units                    1
Acquires                           0
Waiters                            0
Threshold Factor                   8
Threshold                          -1

Here's a description of some of these values:

Configured Units - Indicates the number of concurrent queries that can use compilation memory from the gateway. In the example, 32 concurrent queries can be using memory from the Small gateway (default), eight concurrent queries from the Medium gateway, and one query from the Big gateway. As mentioned earlier, if a query needs more memory than the Small gateway can allocate, it would go to Medium gateway and that query is counted to have taken a unit in both gateways. The larger the amount of compilation memory a query needs, the fewer configured units in a gateway.
Available Units - Indicates the number of slots or units available for concurrent queries to compile from the list of configured units. For example, if 32 units are available, but three queries are currently using compilation memory, then Available Units would be 32 minus 3, or 29 units.
Acquires - Indicates the number of units or slots acquired by queries to compile. If three queries are currently using memory from a gateway, then Acquires = 3.
Waiters - Indicates how many queries are waiting for compilation memory in a gateway. If all the units in a gateway are exhausted, the Waiters value is non-zero that shows the count of waiting queries.
Threshold - Indicates a gateway memory limit that determines where a query gets its memory from, or which gateway it stays in. If a query needs no more than the threshold value, it stays in the small gateway (a query always starts with the small gateway). If it needs more memory for compilation, it would go to the medium one, and if that threshold is still insufficient, it goes to the big gateway. For the small gateway, the threshold factor is 380,000 bytes (could be subject to change in future versions) for x64 platform.
Threshold Factor: Determines the threshold value for each gateway. For the small gateway, since the threshold is predefined, the factor is also set to the same value. The threshold factors for the medium and big gateway are fractions of the total optimizer memory (Overall Memory in the optimization queue) and are set to 12 and 8, respectively. So, if the overall memory is adjusted because other SQL Server memory consumers require memory, the threshold factors would cause the thresholds to be dynamically adjusted as well.
Timeout: Indicates the value in minutes that defines how long a query waits for optimizer memory. If this timeout value is reached, the session stops waiting and raise error 8628 - A time out occurred while waiting to optimize the query. Rerun the query.

Memory brokers

This section provides information about memory brokers that control cached memory, stolen memory, and reserved memory. You can use the information in these tables only for internal diagnostics. Therefore, this information isn't detailed.

MEMORYBROKER_FOR_CACHE (internal)       Value
--------------------------------------- -------------
Allocations                             20040
Rate                                    0
Target Allocations                      3477904
Future Allocations                      0
Overall                                 3919104
Last Notification                       1

MEMORYBROKER_FOR_STEAL (internal)       Value
--------------------------------------- -------------
Allocations                             129872
Rate                                    40
Target Allocations                      3587776
Future Allocations                      0
Overall                                 3919104
Last Notification                       1

MEMORYBROKER_FOR_RESERVE (internal)     Value
--------------------------------------- -------------
Allocations                             0
Rate                                    0
Target Allocations                      3457864
Future Allocations                      0
Overall                                 3919104
Last Notification                       1

MEMORYBROKER_FOR_CACHE (default)        Value
--------------------------------------- -------------
Allocations                             44592
Rate                                    8552
Target Allocations                      3511008
Future Allocations                      0
Overall                                 3919104
Last Notification                       1

MEMORYBROKER_FOR_STEAL (default)        Value
--------------------------------------- -------------
Allocations                             1432
Rate                                    -520
Target Allocations                      3459296
Future Allocations                      0
Overall                                 3919104
Last Notification                       1

MEMORYBROKER_FOR_RESERVE (default)      Value
--------------------------------------- -------------
Allocations                             0
Rate                                    0
Target Allocations                      3919104
Future Allocations                      872608
Overall                                 3919104
Last Notification                       1

Κοινή χρήση μέσω

Use the DBCC MEMORYSTATUS command to monitor memory usage in SQL Server

Introduction

How to use DBCC MEMORYSTATUS

Process/System Counts

Memory Manager

Memory usage with NUMA nodes

Aggregate memory

Buffer pool details

Plan cache

Global Memory Objects

Query memory objects

Optimization memory

Memory brokers

Σχόλια

Πρόσθετοι πόροι