Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 awe versus /3GB switch again

Author  Topic 

kotsas
Yak Posting Veteran

65 Posts

Posted - 2002-05-24 : 03:32:46
I know when AWE is enabled that sql2000 do not dynamically manage the size of the address space. What about if I put /3GB switch? Will Sql 2000 like SQL 7.0 see above 2GB when I put /3GB switch or I must enable AWE? I have active/active configuration and I like when failover occur 2 instances to manage memory dynamically?


setbasedisthetruepath
Used SQL Salesman

992 Posts

Posted - 2002-05-24 : 10:25:09
hmmm....

You've mixed issues in your post. One is memory mapping by the OS, and the other is a description of your clustering setup. They aren't related.

The Windows memory subsystem is a 4Gb address space. The "lower" 2Gb can be used by applications, the "higher" 2Gb is reserved for the OS. Because the application address space is 2Gb, no single application ( including SQL Server ) can allocate more than 2Gb.

The /3GB switch in boot.ini readjusts that allocation, giving 3Gb to applications and 1Gb to the OS. It is used when systems have up to 4Gb of RAM. Past that ( and assuming you have advanced server or datacenter server ) AWE allows SQL Server to allocate up to 64Gb.

quote:

I know when AWE is enabled that sql2000 do not dynamically manage the size of the address space. What about if I put /3GB switch? Will Sql 2000 like SQL 7.0 see above 2GB when I put /3GB switch or I must enable AWE? I have active/active configuration and I like when failover occur 2 instances to manage memory dynamically?



setBasedIsTheTruepath
<O>
Go to Top of Page

chadmat
The Chadinator

1974 Posts

Posted - 2002-05-24 : 15:34:22
I have to correct you a little SetBased...

They are kind of related. If you have AWE enables, and both nodes have fixed memory at say 4GB, then you fail over. If the machine only has 6 or even 8 GB of RAM, you will run into problems, because both SQL Instances can't get 4GB, as well as the OS get what it needs.

If AWE is enabled, you should have your memory setting so that this situation will never occur. (If you have 8GB, set memory to fixed of 3GB on both).

-Chad

Go to Top of Page
   

- Advertisement -