May 26, 2015 at 8:58 am
Set SQL Server max memory. I watched a SQL Server 2005 EE development server die a slow and painful death because SQL Server starved the OS. Once I set max memory that didn't happen again.
I would even do it if running SQL Server 2008 R2 SE on a server with more than 64 GB of ram since SE only uses up to 64 GB.
May 27, 2015 at 1:44 pm
After I install a new SQL Server one of the first things on the check list is to set Max memory. Rule out a potential problem in the future.
May 28, 2015 at 1:11 am
My general rough rule and first setting on a new server is to set it so sql server max memory is 75% of the total available memory. Then see how it goes.
May 28, 2015 at 1:20 am
My general rough rule and first setting on a new server is to set it so sql server max memory is 75% of the total available memory. Then see how it goes.
My servers are generally small (2 to 16GB) and that's fine until server team (who don't understand sql server) go altering the available memory on the VMs and of course never tell me.
They keep trying to take memory away from sql servers and, because their vSphere 5 monitoring tools suggest it from a one off snapshot, they want to run our test Sharepoint server on 608 Mb of RAM and 1 virtual CPU and reduce our (already slow especially for reporting) 2 instances development & test sql server from 2cpu to 1 and from 2Gb memory to 1Gb. Grr!
May 28, 2015 at 8:46 am
I find it interesting that Brent Ozar's sp_Blitz complains if you change the min or max memory settings as a "non-default server config". I appreciate the warning as you can starve either the OS or SQL by misconfiguring those settings, I think it could stand a reasonableness check for the values.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply