Should I enable AWE option when I use "/3gb" parameter?

Should I enable AWE option when I use "/3gb" parameter?

Post by Jackson Chen » Wed, 15 Jan 2003 05:15:50



After adding the parameter "/3gb" in the boot.ini ,
I don't find much more memory could be used.(SQL Server
and MS Search still use up to the default 2GB memory only)
What is the problem ? My seeting like this :

    Operating System : Windows 2000 Server (not advanced)
    DBMS : SQL Server 2000 Enterprise Version
    Setting :

        1). "/3gb" is added in the boot.ini ;
        2). AWE option  is not enabled in SQL Server ;

Should I enable AWE option to make "/3gb" parameter be
effective ? Could AWE option and "/3gb" parameter be used
in Windows 2000 "Advanced" Server only ?  

 
 
 

Should I enable AWE option when I use "/3gb" parameter?

Post by Arvind Shyamsunda » Wed, 15 Jan 2003 13:25:45


Dear Jackson,
I believe you you need to enable AWE to utilize more than the 2GB RAM.
Please follow the instructions in the following MSDN article: Q274750: "HOW
TO: Configure Memory for More Than 2 GB in SQL Server" for detailed
instructions.

HTH,

Arvind S.


Quote:> After adding the parameter "/3gb" in the boot.ini ,
> I don't find much more memory could be used.(SQL Server
> and MS Search still use up to the default 2GB memory only)
> What is the problem ? My seeting like this :

>     Operating System : Windows 2000 Server (not advanced)
>     DBMS : SQL Server 2000 Enterprise Version
>     Setting :

>         1). "/3gb" is added in the boot.ini ;
>         2). AWE option  is not enabled in SQL Server ;

> Should I enable AWE option to make "/3gb" parameter be
> effective ? Could AWE option and "/3gb" parameter be used
> in Windows 2000 "Advanced" Server only ?


 
 
 

Should I enable AWE option when I use "/3gb" parameter?

Post by <n.. » Wed, 15 Jan 2003 17:05:40


You need SQL 2k Enterprise and Win2k Advanced to use either /3gb, AWE, or
both.


Quote:> After adding the parameter "/3gb" in the boot.ini ,
> I don't find much more memory could be used.(SQL Server
> and MS Search still use up to the default 2GB memory only)
> What is the problem ? My seeting like this :

>     Operating System : Windows 2000 Server (not advanced)
>     DBMS : SQL Server 2000 Enterprise Version
>     Setting :

>         1). "/3gb" is added in the boot.ini ;
>         2). AWE option  is not enabled in SQL Server ;

> Should I enable AWE option to make "/3gb" parameter be
> effective ? Could AWE option and "/3gb" parameter be used
> in Windows 2000 "Advanced" Server only ?

 
 
 

1. enabling AWE to use 3GB of memory????

I have a Dell 6650 server with 4Gig of memory.  I added the /3gb switch
to the boot.ini file to use 3gb of memory instead of the 2gb Windows
2000 normally allocates to an application; however, my server has been
periodically freezing since I made this change.  My question is, do I
need to set the AWE Sql option to 1 in order to use 3GB?  Microsoft
seems to indicate that setting this option to 1 is only necessary when
there is more than 4GB of physical memory on the machine.  Can some one
confirm?

(The login the sql server service is running under has the "lock pages
in memory" rights.)

Thanks,
Walter

PS  Here's an example of odd stuff that happens in my SQL Server logs
prior to a server freeze:

Dynamic Memory Manager:  Stolen=115503 OS Reserved=34016
                OS Committed=33984
                OS In Use=23487
                Query Plan=129775 Optimizer=0
                General=8615
                Utilities=163 Connection=241
_______________________________________
Query Memory Manager:  Grants=1 Waiting=0 Maximum=198263
Available=197551
______________________________________________
Buffer Counts:  Commited=338640 Target=338640 Hashed=222737
                InternalReservation=776 ExternalReservation=652 Min Free=256

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

2. AbsolutePage

3. Using ODBC Option: "Failover SQL Server"

4. UniData error message

5. Using ODBC Option "Failover SQL Server"

6. Converting data to Informix from PICK!

7. ObjectPAL for "Using With" option

8. Multi Column cbobox question

9. max of ("...","...","..")

10. Parameter used in "For XML Explicit"

11. VarChar Parameter used for "IN" Clause

12. "DBPROCESS is dead or not enabled"

13. Enabling "DATA ACCESS"