What was your reasoning behind enabling lpim by the way? Thanks for posting some results but now that we know you have lock pages in memory (lpim) enabled the process list is not going to tell us anything of much use. ORDER BY SUM(single_pages_kb+multi_pages_kb) DESC The reliable way to check SQL's memory usage is with the TotalServerMemory perfmon counter.ĬAST(SUM(single_pages_kb+multi_pages_kb) / 1024.0 AS DECIMAL(10, 2)) AS Task manager should never be used to check SQL's memory because it only shows memory allocated via VirtualAlloc, not AllocateUserPhysicalPages and hence gives completely incorrect results when locked pages is enabled (or AWE on 32-bit) He's running locked pages in memory and Task Manager does not report memory allocated using the physical alloc that SQL uses when locked pages is enabled. I have seen this scenario reported before and the OP never got to the bottom of it: Further to that, the majority of the 7.5GB is unnaccounted for in the Processes Tab. I think the OP is saying memory used by sqlservr.exe per Task Manager (count on Processes Tab should include buffer pool for 圆4 SQL) is only 124MB but Task Manager Performance Tab is reporting 7.5GB of the 8GB of physical memory is used.
0 kommentar(er)
