/3Gb option set, but SQL Server use only 1.7Gb....

Hi,
I have setup the /3Gb option in the boot.ini file because my server has 4Gb
of RAM.
But SQL Server still use only 1.7Gb.
on another server, there is no problems, the same parameters and SQL Server
use more then 2Gb of memory!!!
there is anything missing ?
what can I check?
thanks.
Jerome.
Which OS version and edition and SQL Server edition are you using?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:uaW1M4HaFHA.2212@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server has
> 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
> thanks.
> Jerome.
>
|||Jj wrote:
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server
> has 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
> thanks.
> Jerome.
Are you running SQL 2000 Service Pack 4? If so, there's a known issue
with AWE that is going to be addressed with a hotfix in the next week or
two.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:uaW1M4HaFHA.2212@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server has
> 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
Use /pae in boot.ini and enable awe in SQL Server, then your SQL should be
able to consume ca. 3.75 GB of RAM (W2K AS + SQL EE SP3)
Regards
Wojtek
|||Yes, SP4 installed
on a Win 2003 Enterprise edition server
AWE is NOT enable on the server.
For a 4Gb system what is the best option?
/3Gb
/3Gb + AWE
/PAE
/PAE + AWE
/3Gb /PAE
/3Gb /PAE + AWE
?
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl...
> Jj wrote:
> Are you running SQL 2000 Service Pack 4? If so, there's a known issue with
> AWE that is going to be addressed with a hotfix in the next week or two.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
|||"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
> Yes, SP4 installed
> on a Win 2003 Enterprise edition server
> AWE is NOT enable on the server.
> For a 4Gb system what is the best option?
> /3Gb
> /3Gb + AWE
> /PAE
> /PAE + AWE
> /3Gb /PAE
> /3Gb /PAE + AWE
> ?
/3Gb /PAE + AWE
But AFAIK not with SP4... SP4 has some issue with /pae and AWE.
Regards
Wojtek
|||You still need SQL Enterprise Edition to use more than 2GB. It sounds like
you are using Standard Edition of SQL Server. What does @.@.Version show?
Andrew J. Kelly SQL MVP
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
> Yes, SP4 installed
> on a Win 2003 Enterprise edition server
> AWE is NOT enable on the server.
> For a 4Gb system what is the best option?
> /3Gb
> /3Gb + AWE
> /PAE
> /PAE + AWE
> /3Gb /PAE
> /3Gb /PAE + AWE
> ?
>
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl...
>
|||/PAE is only required for > 4 GB. AWE can be enabled before then. And,
/3GB should be enabled all the time up to 16 GB, but on Win2K3, you should
use the USERVA to start scalling back from 3 GB around 12 GB of ram or so.
Again, if you are only using Standard Edition Win2K, /3GB is NOT supported.
Sincerely,
Anthony Thomas

"Wojtek Garwol" <garwol@.usunto.poczta.fm> wrote in message
news:d7qj6e$jsu$1@.nemesis.news.tpi.pl...
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:uaW1M4HaFHA.2212@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have setup the /3Gb option in the boot.ini file because my server has
> 4Gb of RAM.
> But SQL Server still use only 1.7Gb.
> on another server, there is no problems, the same parameters and SQL
> Server use more then 2Gb of memory!!!
> there is anything missing ?
> what can I check?
Use /pae in boot.ini and enable awe in SQL Server, then your SQL should be
able to consume ca. 3.75 GB of RAM (W2K AS + SQL EE SP3)
Regards
Wojtek
|||I think its the standard edition of SQL 2000.
I'll check this.
but...
on another environment the memory usage go up to 2.7gb.
its a Win 2003 Ent. server (SP1) + SQL 2000 enterprise (SP4)
4 Gb of memory, 2.7g used by SQL and 512mb of free memory.
there is no upper limit usage for SQL Server.
the /3Gb option is enabled AWE disabled.
why SQL don't use more memory?
any missing option in this case?
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl...
> You still need SQL Enterprise Edition to use more than 2GB. It sounds
> like you are using Standard Edition of SQL Server. What does @.@.Version
> show?
> --
> Andrew J. Kelly SQL MVP
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl...
>
|||The reason SQL memory allocation is only going up to 2.7G is because a
Win32 process can only address 4G of RAM (without changes to the memory
model, like PAE & AWE). This 4G is split up into 2 components: user
addressable memory & kernel addressable memory. The split is normally
2G/2G but when you specify the /3GB switch in boot.ini this means the OS
will only allocate a maximum of 1G to the kernel for each process. So
this means that when addressing 4G of memory the kernel code will
address 1G and the user code will address 3G of memory (hence the /3GB
switch - it would be more accurate to call it the "/1GB" switch because
that's the bit it's really limiting).
To address more than 4GB of memory you have to either switch to 64-bit
or change the memory management strategy, for example by using PAE &
AWE. But in your case, with 4GB of physical RAM in the box and the /3GB
boot.ini switch enabled, the memory ceiling for SQL Server will be 3GB,
and 2.7GB is getting pretty close. Remember SQL Server will, by
default, release memory when other applications request memory and there
is none left (it tries to maintain a free memory threshold of 10MB by
default) because of the dynamic memory management model SQL has implemented.
HTH
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Jj wrote:

>I think its the standard edition of SQL 2000.
>I'll check this.
>but...
>on another environment the memory usage go up to 2.7gb.
>its a Win 2003 Ent. server (SP1) + SQL 2000 enterprise (SP4)
>4 Gb of memory, 2.7g used by SQL and 512mb of free memory.
>there is no upper limit usage for SQL Server.
>the /3Gb option is enabled AWE disabled.
>why SQL don't use more memory?
>any missing option in this case?
>"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl...
>
>
>