April 11, 2007 at 5:09 pm
I have a Windows Server 2003 Standard Edition with SQL Server 2005 Standard Edition SP2.
This Server has 4GB Physical RAM.
At the moment, the SQL Server can only see 2GB RAM.
I wish to allocate another 1GB RAM to SQL Server to total it to 3GB and that would leave 1GB to the Operating System.
The question is what is the order that I have to do this in as BOL doesn't actually state the order.
Is this order correct?
1. Place the /3GB swicth in boot.ini
2. Configure "lock pages in memory" for the startup account that starts SQL Server
3. Enable AWE on SQL Server with sp_configure
4. Configure MIN & MAX Memory on SQL Server.
April 12, 2007 at 3:12 am
Trigger,
there's no need to enable AWE. And from what I understood, you only need the "lock pages in memory" option on a 64-bit system. So if you're running a 32-bit system just use steps 1 and 4.
On a 64-bit system only steps 2 and 4 are necessary.
Markus
[font="Verdana"]Markus Bohse[/font]
April 12, 2007 at 4:38 pm
April 14, 2007 at 7:48 pm
"you only enable AWE when you wish SQL Server to see beyond 4GB RAM?"
no, you enable AWE when you wish SQL to see beyond your process's user mode virtual address space (UM-VAS).
on 32 bit UM-VAS is 2GB. on x64 machines, SQL 32 bit running
under wow mode has 4GB UM-VAS.
From what i know, the overhaeds of AWE (for machines under 4GB of RAM) would outweight gains.
just a side note: adding /3GB in boot.ini is an operating system level operation. which means every process on the server would get this change. This also limits OS's ability to see only a max of 16 GB RAM.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply