title: How to analyze 'dbcc memorystatus' result in SQL Server 2008
body: <p>Currently I am facing a SQL memory pressure issue. i have run <code>dbcc memorystatus</code>, here is part of my result:</p>
  
  <pre><code>Memory Manager                           KB
  ---------------------------------------- -----------
  VM Reserved                              23617160
  VM Committed                             14818444
  Locked Pages Allocated                   0
  Reserved Memory                          1024
  Reserved Memory In Use                   0
  
  
  Memory node Id = 0                       KB
  ---------------------------------------- -----------
  VM Reserved                              23613512
  VM Committed                             14814908
  Locked Pages Allocated                   0
  MultiPage Allocator                      387400
  SinglePage Allocator                     3265000
  
  
  MEMORYCLERK_SQLBUFFERPOOL (node 0)       KB
  ---------------------------------------- -----------
  VM Reserved                              16809984
  VM Committed                             14184208
  Locked Pages Allocated                   0
  SM Reserved                              0
  SM Committed                             0
  SinglePage Allocator                     0
  MultiPage Allocator                      408
  
  MEMORYCLERK_SQLCLR (node 0)              KB
  ---------------------------------------- -----------
  VM Reserved                              6311612
  VM Committed                             141616
  Locked Pages Allocated                   0
  SM Reserved                              0
  SM Committed                             0
  SinglePage Allocator                     1456
  MultiPage Allocator                      20144
  
  CACHESTORE_SQLCP (node 0)                KB
  ---------------------------------------- -----------
  VM Reserved                              0
  VM Committed                             0
  Locked Pages Allocated                   0
  SM Reserved                              0
  SM Committed                             0
  SinglePage Allocator                     3101784
  MultiPage Allocator                      300328
  
  Buffer Pool                              Value
  ---------------------------------------- -----------
  Committed                                1742946
  Target                                   1742946
  Database                                 1333883
  Dirty                                    940
  In IO                                    1
  Latched                                  18
  Free                                     89
  Stolen                                   408974
  Reserved                                 2080
  Visible                                  1742946
  Stolen Potential                         1579938
  Limiting Factor                          13
  Last OOM Factor                          0
  Page Life Expectancy                     5463
  
  Process/System Counts                    Value
  ---------------------------------------- --------------------
  Available Physical Memory                258572288
  Available Virtual Memory                 8771398631424
  Available Paging File                    16030617600
  Working Set                              15225597952
  Percent of Committed Memory in WS        100
  Page Faults                              305556823
  System physical memory high              1
  System physical memory low               0
  Process physical memory low              0
  Process virtual memory low               0
  
  Procedure Cache                          Value
  ---------------------------------------- -----------
  TotalProcs                               11382
  TotalPages                               430160
  InUsePages                               28
  </code></pre>
  
  <p>Can you lead me to analyze this result ?</p>
  
  <p>Is it a lot execute plan have been cached causing the memory issue or other reasons?</p>