Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Another Max Memory Question Expand / Collapse
Posted Thursday, October 3, 2013 4:36 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Thursday, October 20, 2016 11:40 AM
Points: 626, Visits: 1,948
We're planning to install a named instance of SQL 2008 R2 on a server that already has a default instance. Naturally we'll have to reduce the Max memory setting on the default instance to prevent the two instances and OS from wrestling over memory. The server has 32GB of RAM and the default instance Max memory setting is currenly 27GB.

The total size of all databases on the named instance will be less than 3GB. Is there any additional benefit to setting the max memory to much more then the size of the databases? I'd prefer to give the named instance the minimum amount it needs and the default instance as much as possible because the default instance hosts about 100GB of data for mutliple applications.
Post #1501377
Posted Monday, October 7, 2013 8:15 AM



Group: General Forum Members
Last Login: Tuesday, July 19, 2016 4:34 AM
Points: 2,850, Visits: 4,076
Based on the load you have mentioned here.yes i think below ratio can work.

OS - 4 GB
Named- 4/6 GB
Default -- 22/24 GB

BUt keep the memory utilization on your RADAR for few weeks.

I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1502157
Posted Monday, October 28, 2013 3:41 PM


Group: General Forum Members
Last Login: Wednesday, April 27, 2016 3:18 AM
Points: 2,687, Visits: 715
be aware that the sql memory options are for buffer cache and not the other various memory pools. I generally never use lock pages in memory as this allows you to see how memory is actually being utilised. Note that Tempdb may use as much memory or greater than your database(s)
As with any such scenario you have to monitor and trend to best tune the resources to the demands of the server. I'm assuming this is all x64 so watch your other memory pools.
My advice - take a estimate at what you think is fair - then monitor ( record to a table ) and adjust to suit. Taking pot luck might not be the best choice!
Although I have no affiliation to SQL Diagnostic Manager I'd suggest this as a useful tool to assist.

The GrumpyOldDBA
Post #1509127
Posted Sunday, November 24, 2013 2:12 PM



Group: General Forum Members
Last Login: Thursday, December 1, 2016 6:49 AM
Points: 1,634, Visits: 1,621
One thing you can do is to give the new instance an optimistic amount of memory (more than it can use) and then monitor to see how much it actually does use for a while and then adjust your memory settings to a final value.

My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master, SQL Server MVP
Database Engineer at BlueMountain Capital Management
Post #1517124
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse