jbarton221
asked on
SQL Server 2000 \3gb PAE Windows Server 2003 Enterprise Boot.ini configuration?
I am running Windows Server 2003 R2 Enterprise Edition, using IIS, and SQL Server 2000 Enterprise Edition. It as a 6 month old Dell server running 2 quad core processors with 8GB of RAM. I have not changed any entries to the boot.ini or with SQL Server to take advantage of the memory. I am looking for the best way to utilize the hardware in the machine???? I am somewhat familiar with the /3gb option and a little with PAE and AWE through researching. What is the best configuration to utilize the hardware in this server?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
how big are your sql database you want to try and load as much as you can into memory but if it is quite big i would then be careful otherwise sql wil kill the server. you got 1 gb for OS so leaves you with 7GB check with your software provider and set accordinly
ASKER
It looks like the databases add up to just over 5GB, so should I set it to 6GB maximum?
yes idealy you want to load the database into ram but if you are using the server for other applications you want to let them have a little
ASKER
When I added all of the switches I got complaints that it was running slow. When you look at the running apps in task manager does it not show the extended 4GB for memory useage on those apps?
if you dont set the maxium ram amount in sql then it will hog and take it all have you set this
ASKER
We set the maximum, but how can I check that it is using the extended 4GB. Example:
When I set the \3GB switch in the boot.ini and leave the maximum memory to default in SQL the sqllogon process is at 2.7GB
When I use the \AWE switch and set the maximum memory to 6GB that same process is only at 96,000
When I set the \3GB switch in the boot.ini and leave the maximum memory to default in SQL the sqllogon process is at 2.7GB
When I use the \AWE switch and set the maximum memory to 6GB that same process is only at 96,000
To find out use Performance Monitor (total SQL server memory, target SQL server memory), not Task Manager
ASKER