Re: SQL Server user 2GB> ram


Hello guys,

I have enable the AWE using the following scripts:

sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO

However, when I monitor the SQL Server Performance Monitor Total Server
Memory (KB) counter. It show up 1.7 GB, instead of 6 GB. Do you know why?

"LaRoux" wrote:

AWE is the feature you need to make this work. From BOL:

awe enabled Option
In Microsoft® SQL ServerT 2000, you can use the Microsoft Windows® 2000
Address Windowing Extensions (AWE) API to support up to a maximum of 64
gigabytes (GB) of physical memory. The specific amount of memory you can use
depends on hardware configuration and operating system support.



Note This feature is available only in the SQL Server 2000 Enterprise and
Developer editions.


Enabling AWE
To enable AWE, set awe enabled to 1. SQL Server will reserve almost all
available memory, leaving 128 megabytes (MB) or less, unless a value has
been specified for max server memory.

If the option has been successfully enabled, the message "Address Windowing
Extension enabled" is printed in the SQL Server error log when the instance
of SQL Server 2000 is started.

awe enabled is an advanced option. If you are using the sp_configure system
stored procedure to change the setting, you can change awe enabled only when
show advanced options is set to 1. You must restart the instance of SQL
Server 2000 for changes to take effect.

Disabling AWE
To disable AWE, set awe enabled to 0. This setting is the default. The AWE
API is not used. SQL Server 2000 operates in a normal dynamic memory
allocation mode and is limited to 3 GB of physical memory.

Usage Considerations
Before enabling AWE, consider the following:

a.. When awe enabled is set to 1, instances of SQL Server 2000 do not
dynamically manage the size of the address space. SQL Server will reserve
and lock almost all available memory (or the value of max server memory if
the option has been set) when the server is started. It is strongly
recommended that you set a value for the max server memory option each time
you enable AWE. Otherwise other applications or instances of SQL Server 2000
will have less than 128 MB of physical memory in which to run.


b.. If the total available memory is less than 3 GB, the instance of SQL
Server 2000 will be started in non-AWE mode even if awe enabled is set to 1.
In this situation, you do not need to manage AWE memory because dynamic
memory allocation is used automatically.


c.. You can determine the amount of memory you can safely allocate to
instances of SQL Server 2000 by identifying how much memory is available
after all other applications to be used on the computer have been started.
Use the SQL Server Performance Monitor Total Server Memory (KB) counter to
determine how much memory is allocated by the instance of SQL Server running
in AWE mode. Configure the max server memory option to leave some additional
memory free to allow for the varying needs of other applications and Windows
2000. For more information, see Monitoring Memory Usage.



Important Using the awe enabled option and the max server memory setting
can have a performance impact on other applications or on SQL Server running
in a multi-instance or cluster environment. For more information about using
AWE memory, see Managing AWE Memory.


Example
The following example shows how to enable AWE and configure a limit of 6 GB
for max server memory:

sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
"kent kent" <kentkent@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A1E252CE-9DFF-464D-A4E5-4B461CEB84BF@xxxxxxxxxxxxxxxx
Hello guys,

We have a Window Server 2003 EE and SQL 2000 EE Server with 32GB of Ram.
How to enable SQL Server to use more than 2GB of Ram. Our System admin
said
if our Server has more than 16 GB or Ram, then we cannot enable the 3GB
switch in the boot.ini file. As a result, SQL Server can't use more than
2GB
of Ram. Is that ture or not?

Thanks,



.

Relevant Pages

  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • Re: FTS Performance in SQL 2005
    ... I don't think you have left enough memory for the OS and MSSearch. ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ...
    (microsoft.public.sqlserver.fulltext)
  • RE: Insufficient memory Available
    ... Insufficient memory available. ... within the scope of SQL Server. ... "MemToLeave" area. ...
    (microsoft.public.sqlserver.server)
  • RE: server problems
    ... This newsgroup only focuses on SBS technical issues. ... >Thread-Topic: server problems ... >> web proxy service or SQL Server will normally use large memory. ...
    (microsoft.public.windows.server.sbs)
  • RE: server problems
    ... > web proxy service or SQL Server will normally use large memory. ... > the SBS server and sends the alert when the value reaches the threshold. ...
    (microsoft.public.windows.server.sbs)
Loading