October 2, 2003 at 11:55 am
I am running SQL Server Enterprise Edition on a Windows 2000 advanced Server OS. The server has 8 GB of RAM and I am trying to figure out how to utilize the AWE settings within SQL server to grab and utilize RAM.
So Far I have ......
1. Added the /PAE setting to the boot.ini file.
2. Ran the following script in master on the local instance of SQL Server.(There are 2 other instances on the Box.)
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Is there anything else I need to do? Plus how can I confirm the process has worked?
Any help would be greatly appreciated.
Thanks
October 2, 2003 at 12:13 pm
To use AWE memory, you must run the SQL Server 2000 database engine under a Windows 2000 account that has been assigned the Windows 2000 lock pages in memory privilege.
Use System Monitor (Performance Monitor) to retrieve information on SQL Server memory usage and available memory.
Use Total Server Memory (KB) performance counter, activated through System Monitor, or select the memory usage from sysperfinfo to see memory being consumed by SQL Server.
October 3, 2003 at 1:23 am
With your configuration, you should also set the /3gb switch in boot.ini.
If you allocate 6gb as in your example, you aren't leaving much memory for the other 2 instances that you say are running on the same box.
When SQL Server Uses AWE memory, it cannot dynamically allocate and de-allocate memory, so you may starve the other 2 instances.
October 3, 2003 at 8:26 am
The /3gb switch in the boot.ini is correct. I just set up a server that runs with 8gb memory and with the correct switches and configurations listed above it allocates 6gb to SQL and 2gb for OS.
Edited by - brentolsen on 10/03/2003 08:26:56 AM
October 3, 2003 at 9:35 am
I am afraid that I have to object on the use of the /3GB switch in your environment.
If you were only running one SQL instance, using the switch would be fine. Using the switch reduces the RAM available to the OS down to 1GB. This reduces resources available to manage your applications and file system access which could become an issue with more than one application being served.
October 3, 2003 at 10:10 pm
With the /3GB enabled, system will allocate 3GB for applications including SQL Serevr and leave itself 1GB. It also uses memeory within 1GB to manage the memory that is beyond 4GB. I have seen SAP notes that guides to configure SAP application and SQL Server in same server, /3GB is recommended if physical memory is less than 8GB.
Edited by - allen_cui on 10/03/2003 10:10:39 PM
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply