June 2, 2008 at 12:00 pm
I just went through a previous post on pretty much the same topic, but I'm still confused:
SQL Server 2005 max memory and /3GB switch
http://qa.sqlservercentral.com/Forums/Topic412378-146-1.aspx
Here is my situation:
OS: Windows Server 2003 R2 Enterprise Edition Service Pack 2
RAM: 8 GB
I want to enable my SQL instance to 'see' 3 GB of VAS (I have 2 other SQL instances on the same box, each limited to 2 GB of VAS).
The SQL instance in question is on SQL 2005 SP2 (Standard Edn).
Do I just need to turn on the 3-GB switch and enable AWE?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
June 2, 2008 at 12:38 pm
Add the /3GB switch in BOOT.ini and enable AWE using SP_Configure...
MohammedU
Microsoft SQL Server MVP
June 2, 2008 at 12:39 pm
Here is the MS article...
How to configure SQL Server to use more than 2 GB of physical memory
http://support.microsoft.com/kb/274750
MohammedU
Microsoft SQL Server MVP
June 2, 2008 at 12:41 pm
MohammedU (6/2/2008)
Here is the MS article...How to configure SQL Server to use more than 2 GB of physical memory
Thanks, but that link does not apply in my case (I have SQL Server 2005 Standard Edition):
from http://support.microsoft.com/kb/274750
APPLIES TO
• Microsoft SQL Server 2000 Enterprise Edition
• Microsoft SQL Server 7.0 Standard Edition
• Microsoft SQL Server 2005 Enterprise Edition
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
June 2, 2008 at 12:48 pm
you don't have enough memory and if you enable the /3gb switch all instances will share the 3gb vas. I think there may be some confusion over the bottom memory in x32 - there is only 1 2gb vas and all apps share it, so each instance does not have it's own 2gb of physical memory - the actual memory is allocated through virtual memory and physical memory.
I'd figure you need to forget the 3gb switch ( I'd really really advise not trying to run three sql servers with only 1 gb ram for the o/s ) just enable awe for each instance and peg max memory at 2gb. If you have a modern server all the memory should be available.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
June 2, 2008 at 12:54 pm
It applies to all Standard edition too but in your case you have many instances...
How you want to take the advantage of /3GB AND how do you want to configure the SQL memory...
MohammedU
Microsoft SQL Server MVP
June 2, 2008 at 12:59 pm
colin Leversuch-Roberts (6/2/2008)
you don't have enough memory and if you enable the /3gb switch all instances will share the 3gb vas. I think there may be some confusion over the bottom memory in x32 - there is only 1 2gb vas and all apps share it, so each instance does not have it's own 2gb of physical memory - the actual memory is allocated through virtual memory and physical memory.I'd figure you need to forget the 3gb switch ( I'd really really advise not trying to run three sql servers with only 1 gb ram for the o/s ) just enable awe for each instance and peg max memory at 2gb. If you have a modern server all the memory should be available.
Thank you for the response.
I was thinking of allocating memory as follows:
instance1: 3 GB
instance2: 2 GB
instance3: 2 GB
OS: 1 GB
If I'm reading you correctly, leaving the OS with just 1 GB of memory is not advisable in this situation?
So perhaps I could configure it this way?
instance1: 3 GB <-- enable AWE for this instance only
instance2: 2 GB
instance3: 1 GB
OS: 2 GB
Would that work?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply