You might have noticed that with some Microsoft SQL Server instances you can’t see the allocated memory in Windows Task Manager. If you look at the total allocated memory in Task Manager, it looks as it normally does on a server with SQL Server on it, its just about maxed out. But if you look in the process list, no process is taking up the memory. You would expect the SQL Server process to have allocated almost all of the servers memory, but no. So what is going on? This happens if you activate Lock Pages in Memory for the SQL Server service account, and you can verify how much memory SQL Server actually uses by running this script: select SUM(virtual_memory_reserved_kb)/1024/1024 as Allocated_VM_in_GB from sys.dm_os_memory_clerks
If you need help with optimizing your SQL Server environment, you can always contact us!