sql server 2008 r2 64 bit for windows 10

Here is a good primer on the debate and one of many articles and my own experience that helped shape my opinion: Great SQL Server Debates: Lock Pages in Memory (12 December 2011) by Jonathan Kehayias Some prefer to enable lpim on 圆4 Windows Server 2008 R2 running SQL Server 2008 R2 by default, and others prefer (including myself) to leave lpim disabled unless the database server exhibits specific behavior that signals there may be a benefit to enabling lpim.

There is a great debate about this in the SQL Serevr community.

also memory may boost performance when paging memory to disk is expected. SQL service accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk. Yes, that is correct, lpim is off by default but you have it turned on and you still have not told us why you enabled it.įor this reason enable LPIM in 圆4 operating system. By default, this setting is turned off on 64-bit systems, Lock Pages in Memory is a setting that can be set on 64-bit operating systems that essentially tell Windows not to swap out SQL Server memory to disk. WHERE counter_name = 'Total Server Memory (KB)' SELECT CAST(CAST(value_in_use AS INT) / 1024.0 AS DECIMAL(20, 2)) 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.

Sql server 2008 r2 64 bit for windows 10