Skip to main content
6 events
when toggle format what by license comment
Apr 22, 2015 at 9:34 comment added slinkoff yes you're correct but low memory events shouldn't be happening unless there are pressures on the VM from other processes (shouldn't be running anything other than SQL on the VM) or memory pressure on the host (shouldn't be running that tight and mem priority should be given to SQL over other VMs anyway). Upshot is the memory stays once SQL grows into it which it inevitably will. You can use dynamic with LPIM but don't expect it to move up AND down as SQL doesn't work like that. It's just going to move up so either expect that or use dynamic to find the sweetspot and set that level to static
Apr 22, 2015 at 9:29 history edited slinkoff CC BY-SA 3.0
deleted 18 characters in body
Apr 21, 2015 at 19:26 comment added Tom I don't believe your remark about LPIM is correct in regards to the hypervisor grabbing back memory. My understanding is that where as previously the hypervisor would grab memory back from processes not in the buffer pool first, now that in SQL 2012 most things are in the buffer pool SQL handles the paging out to disk in a controlled manner in response to low memory events. i.e. it still pages out things from the buffer pool even with LPIM just in an optimised way now.
Apr 21, 2015 at 10:04 comment added Spörri The VMWare best practices guide for SQL Server is pretty clear about dynamic allocation. I do not think that there are any reason that HyperV does this much better than VMWare or Xen or any other hypervisor for the reasons @slinkoff mentions: 4.3.4.2. Tier 1 SQL Server workloads Achieving adequate performance is the primary goal. Consider setting the memory reservation equal to the provisioned memory, to avoid ballooning or swapping. vmware.com/files/pdf/solutions/…
Apr 21, 2015 at 9:53 review First posts
Apr 21, 2015 at 10:16
Apr 21, 2015 at 9:52 history answered slinkoff CC BY-SA 3.0