June 5, 2013 at 11:33 am
Not sure if this is the correct forum, but it appears that the single instance 2012 SQL Server 2012 64 Bit Enterprise with 225 Gig allocated to SQL running on VMWare is not allocating the correct memory. We have Minimum memory setup for 200 Gig and the Maximum for 225 Gig and the SQL server only is using roughly 20 Gig as viewed through SQL Sentry. The Page Life Expectancy is only round 5 to 8 and should be up around 300, so I'm not sure if anyone else has had this problem?
Any assistance would be appreciated or I can provide additional information as needed.
Thanks
June 10, 2013 at 3:45 am
Minimum doesn't mean it will start off at the min.
All it means is once it reaches the minimum threshold, it will never release it back to the OS when it doesn't need it anymore.
June 10, 2013 at 4:05 am
Check the VM settings to ensure that the VM really does have that much memory and doesn't just appear to have it. Make sure the VM host isn't stealing back SQL's memory.
Page life expectancy of 300 is a very old recommendation that was barely valid when SQL usually had less than 4GB of memory, it's a completely incorrect guideline these days being way too low. A server with 200GB with a page life expectancy of 15000 is probably indicated as under severe memory pressure.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply