SQL SQLExpress: boot

Showing posts with label boot. Show all posts

Tuesday, March 20, 2012

/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.
"Jéjé" <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.
>|||Jéjé 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|||"Jéjé" <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...
> Jéjé 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|||"Jéjé" <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
"Jéjé" <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...
>> Jéjé 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
>|||/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...
"Jéjé" <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
>
> "Jéjé" <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...
>> Jéjé 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
>>
>|||This is a multi-part message in MIME format.
--030301010703050100030701
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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
Jéjé 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...
>
>>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
>>
>>"Jéjé" <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...
>>
>>Jéjé 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
>>
>>
>>
>
>
--030301010703050100030701
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>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 
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson | database administrator
| mallesons stephen jaques 
T +61 (2) 9296 3668 | F +61
(2) 9296 3885 | M +61
(408) 675 907 
E
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> | W <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a> 
</div>
 
 
Jéjé wrote:
<blockquote cite="miduIfJy7IcFHA.2688@.TK2MSFTNGP14.phx.gbl" type="cite">
<pre wrap="">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" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:sqlmvpnooospam@.shadhawk.com"><sqlmvpnooospam@.shadhawk.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl">news:O8Sh0AQaFHA.3876@.TK2MSFTNGP12.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">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
"Jéjé" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:willgart_A_@.hotmail_A_.com"><willgart_A_@.hotmail_A_.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl">news:uJz3PVKaFHA.612@.TK2MSFTNGP12.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">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" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:david.gugick-nospam@.quest.com"><david.gugick-nospam@.quest.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl">news:eYe9KLIaFHA.616@.TK2MSFTNGP12.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Jéjé wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">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
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=www.imceda.com</a>">http://www.imceda.com">www.imceda.com</a>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=www.quest.com</a>">http://www.quest.com">www.quest.com</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!-->
</pre>
</blockquote>
</body>
</html>
--030301010703050100030701--|||The other .3GB is used by MemToLeave and does not show in Task manager like
the memory pool does. That is perfectly normal for 4GB of ram with /3GB set
and Enterprise Edition.
--
Andrew J. Kelly SQL MVP
"Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:uIfJy7IcFHA.2688@.TK2MSFTNGP14.phx.gbl...
>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
>>
>> "Jéjé" <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...
>> Jéjé 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
>>
>>
>

Monday, March 19, 2012

/3GB benifits

What are the benifits of settings the 3gb switch and the userva=3030 in the
boot.ini of sql server 2000? thanks.
windows 2003 enterprise
4gb ram
sql server enterpriseHi,
Read the below article for more details.
http://www.sql-server-performance.com/awe_memory.asp
Thnks
Hari
SQL Server MVP
"Gabe Matteson" <gmatteson@.inquery.biz.nospam> wrote in message
news:%2366kqs4TFHA.1796@.TK2MSFTNGP15.phx.gbl...
> What are the benifits of settings the 3gb switch and the userva=3030 in
the
> boot.ini of sql server 2000? thanks.
> windows 2003 enterprise
> 4gb ram
> sql server enterprise
>

/3GB and Maximum server memory

Also,
you really should set the limit for this to about 2.5-3GB to keep from
starving the OS and other necessary items of RAM.
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Pieter" <pieterNOSPAMcoucke@.hotmail.com> wrote in message
news:u5h1fb6mIHA.3636@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a 32-bit SQL Server 2005 Enterprise Edition with 4GB of memory. I
> activated the /3GB switch in the boot.ini, but I still can't setthe
> Maximum server memory any higher than 2147483647. What should I do else? I
> presume I should be able to set it until 3 gigabytes now?
>
> Any help will be really appreciated,
>
> Thansk a lot in advance,
>
> Pieter
> This is my boot.ini:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws Server 2003,
> Standard" /noexecute=optout /fastdetect /3GB
>
|||Hi,
Indeed: In the mean time (when looking at the Task Manager) SQL Server is
using allmost 3 gigabytes, which is perfect!
Regarding the 2147483647: when you right click on the Server in the SQL
Server Management Studio, choose properties, and than Memory, you see the
Maximum server memory. But I guess it has nothing to do with it :-)
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:8DEA94EC-ACD9-4C2F-8C93-FE8B24FF7F94@.microsoft.com...[vbcol=seagreen]
> With /3GB switch alone, you should be able to see SQLServer:Buffer
> Manager\Total Pages or SQLServer:Memory Manager\Total Server Memory
> (KB)--both measuring the buffer pool--reach more than 2GB. But you
> probably
> won't see the buffer pool reach 3GB. Maybe, you didn't drive the SQL
> instance
> hard enough for it to use more than what you reported.
> See
> http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
> for an exmaple.
> BTW, how did you get the 2147483647 number?
> Linchi
> "Pieter" wrote:

/3GB and Maximum server memory

Hi,
I have a 32-bit SQL Server 2005 Enterprise Edition with 4GB of memory. I
activated the /3GB switch in the boot.ini, but I still can't setthe Maximum
server memory any higher than 2147483647. What should I do else? I presume I
should be able to set it until 3 gigabytes now?
Any help will be really appreciated,
Thansk a lot in advance,
Pieter
This is my boot.ini:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard"
/noexecute=optout /fastdetect /3GBWith /3GB switch alone, you should be able to see SQLServer:Buffer
Manager\Total Pages or SQLServer:Memory Manager\Total Server Memory
(KB)--both measuring the buffer pool--reach more than 2GB. But you probably
won't see the buffer pool reach 3GB. Maybe, you didn't drive the SQL instance
hard enough for it to use more than what you reported.
See
http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx for an exmaple.
BTW, how did you get the 2147483647 number?
Linchi
"Pieter" wrote:
> Hi,
> I have a 32-bit SQL Server 2005 Enterprise Edition with 4GB of memory. I
> activated the /3GB switch in the boot.ini, but I still can't setthe Maximum
> server memory any higher than 2147483647. What should I do else? I presume I
> should be able to set it until 3 gigabytes now?
>
> Any help will be really appreciated,
>
> Thansk a lot in advance,
>
> Pieter
> This is my boot.ini:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard"
> /noexecute=optout /fastdetect /3GB
>
>|||IIRC, that setting is in MEGABYTES, so it is far more than 4GB. :) Also,
you really should set the limit for this to about 2.5-3GB to keep from
starving the OS and other necessary items of RAM.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Pieter" <pieterNOSPAMcoucke@.hotmail.com> wrote in message
news:u5h1fb6mIHA.3636@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a 32-bit SQL Server 2005 Enterprise Edition with 4GB of memory. I
> activated the /3GB switch in the boot.ini, but I still can't setthe
> Maximum server memory any higher than 2147483647. What should I do else? I
> presume I should be able to set it until 3 gigabytes now?
>
> Any help will be really appreciated,
>
> Thansk a lot in advance,
>
> Pieter
> This is my boot.ini:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
> Standard" /noexecute=optout /fastdetect /3GB
>|||Hi,
Indeed: In the mean time (when looking at the Task Manager) SQL Server is
using allmost 3 gigabytes, which is perfect!
Regarding the 2147483647: when you right click on the Server in the SQL
Server Management Studio, choose properties, and than Memory, you see the
Maximum server memory. But I guess it has nothing to do with it :-)
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:8DEA94EC-ACD9-4C2F-8C93-FE8B24FF7F94@.microsoft.com...
> With /3GB switch alone, you should be able to see SQLServer:Buffer
> Manager\Total Pages or SQLServer:Memory Manager\Total Server Memory
> (KB)--both measuring the buffer pool--reach more than 2GB. But you
> probably
> won't see the buffer pool reach 3GB. Maybe, you didn't drive the SQL
> instance
> hard enough for it to use more than what you reported.
> See
> http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
> for an exmaple.
> BTW, how did you get the 2147483647 number?
> Linchi
> "Pieter" wrote:
>> Hi,
>> I have a 32-bit SQL Server 2005 Enterprise Edition with 4GB of memory. I
>> activated the /3GB switch in the boot.ini, but I still can't setthe
>> Maximum
>> server memory any higher than 2147483647. What should I do else? I
>> presume I
>> should be able to set it until 3 gigabytes now?
>>
>> Any help will be really appreciated,
>>
>> Thansk a lot in advance,
>>
>> Pieter
>> This is my boot.ini:
>> [boot loader]
>> timeout=30
>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
>> Standard"
>> /noexecute=optout /fastdetect /3GB
>>

/3GB

I've been doing some research on whether or not to use the /3GB switch, and
/PAE, in boot.ini but seem that I find contradicting information.
This article by Brian Moran seems to indicate I should use it, and I have
the utmost respect for Brian.
http://www.sqlmag.com/Article/Artic...
of_Memory.html
But I seem to see other articles by MS that either caution against it, or
say it should only be used with certain flavors or OS. And I can't even
find my OS in any of the articles.
I'm using Windows 2003 R2, SQL 2k sp4, on a Proliant 580 with 4GB of ram.
My box is a dedicated SQL Server. I am, temporarily, running IIS and
Reporting Services on the same box. Those will be offloaded to another
server shortly.
Can anyone tell me conclusively whether or not I should use the /3GB switch?
Thanks, AndreUse the /3GB, but don't use the /PAE. Reevaluate after you move IIS and SSRS
off of the box.
Since SQL 2000 can't access memory over 3GB without /PAE, and since /PEA
requires a large memory block (up to 1GB) just to manage memory, in your
scenario, you may actually be causing a reduction to the memory available to
SQL Server.
Configuration -Enabling AWE Memory for SQL Server
http://msdn2.microsoft.com/en-us/library/ms190673.aspx
Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Andre" <no@.spam.com> wrote in message
news:%23DJkotWFHHA.1252@.TK2MSFTNGP02.phx.gbl...
> I've been doing some research on whether or not to use the /3GB switch,
> and /PAE, in boot.ini but seem that I find contradicting information.
> This article by Brian Moran seems to indicate I should use it, and I have
> the utmost respect for Brian.
> http://www.sqlmag.com/Article/Artic..._of_Memory.html
> But I seem to see other articles by MS that either caution against it, or
> say it should only be used with certain flavors or OS. And I can't even
> find my OS in any of the articles.
> I'm using Windows 2003 R2, SQL 2k sp4, on a Proliant 580 with 4GB of ram.
> My box is a dedicated SQL Server. I am, temporarily, running IIS and
> Reporting Services on the same box. Those will be offloaded to another
> server shortly.
> Can anyone tell me conclusively whether or not I should use the /3GB
> switch?
> Thanks, Andre
>

/3gb

I have SQL Server2000 Ent. sitting on Win2003 Ent. with 4GB RAM.
What are my options to best use the RAM?
1. /3GB in Boot.ini and AWE not enabled
2. /3GB in Boot.ini and AWE enabled.
If AWE is not enabled and I have 4GB with /3GB in boot.ini, do I STILL need
to set the MAX SERVER MEMORY to 3GB? If so, I cannot, since the MAX SERVER
MEMORY datatype is INT and can only take 2GB
Can anyone adviseIt depends on how much memory you need for the operating system plus other
stuff you may have on the server. 1GB is great but with a simple server
with just SQL Server and SQL Agent running 512 will be fine. Using only
/3GB is simple and works you could combine them and allow for 3GB of linear
memory and 500MB for AWE.
The configure value for memory is in MB so an int is plenty big enough. See
BOL for details.
"Miles Obrien" <Miles Obrien@.discussions.microsoft.com> wrote in message
news:E1F0F023-61D5-4DC2-BD9F-C511570E371A@.microsoft.com...
>I have SQL Server2000 Ent. sitting on Win2003 Ent. with 4GB RAM.
> What are my options to best use the RAM?
> 1. /3GB in Boot.ini and AWE not enabled
> 2. /3GB in Boot.ini and AWE enabled.
> If AWE is not enabled and I have 4GB with /3GB in boot.ini, do I STILL
> need
> to set the MAX SERVER MEMORY to 3GB? If so, I cannot, since the MAX SERVER
> MEMORY datatype is INT and can only take 2GB
> Can anyone advise|||Thks Danny.
Actually all I wanted to know was, if I set /3GB and do not want to turn on
AWE, how do I set the MAX SERVER MEMORY to 3GB when it has a datatype of
INT?
Or - with AWE disabled and /3GB in Boot.ini how do I know SQL SERVER (or
tell it to) use 3GB of RAM?
"Danny" wrote:
> It depends on how much memory you need for the operating system plus other
> stuff you may have on the server. 1GB is great but with a simple server
> with just SQL Server and SQL Agent running 512 will be fine. Using only
> /3GB is simple and works you could combine them and allow for 3GB of linear
> memory and 500MB for AWE.
> The configure value for memory is in MB so an int is plenty big enough. See
> BOL for details.
> "Miles Obrien" <Miles Obrien@.discussions.microsoft.com> wrote in message
> news:E1F0F023-61D5-4DC2-BD9F-C511570E371A@.microsoft.com...
> >I have SQL Server2000 Ent. sitting on Win2003 Ent. with 4GB RAM.
> >
> > What are my options to best use the RAM?
> > 1. /3GB in Boot.ini and AWE not enabled
> > 2. /3GB in Boot.ini and AWE enabled.
> >
> > If AWE is not enabled and I have 4GB with /3GB in boot.ini, do I STILL
> > need
> > to set the MAX SERVER MEMORY to 3GB? If so, I cannot, since the MAX SERVER
> > MEMORY datatype is INT and can only take 2GB
> >
> > Can anyone advise
>
>|||> Actually all I wanted to know was, if I set /3GB and do not want to turn
> on
> AWE, how do I set the MAX SERVER MEMORY to 3GB when it has a datatype of
> INT?
The 'max server memory' specification is in MB. 3 GB = 3072 MB.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Miles Obrien" <MilesObrien@.discussions.microsoft.com> wrote in message
news:47EAA1B3-82F1-4091-AC58-A08EF90BAD90@.microsoft.com...
> Thks Danny.
> Actually all I wanted to know was, if I set /3GB and do not want to turn
> on
> AWE, how do I set the MAX SERVER MEMORY to 3GB when it has a datatype of
> INT?
> Or - with AWE disabled and /3GB in Boot.ini how do I know SQL SERVER (or
> tell it to) use 3GB of RAM?
> "Danny" wrote:
>> It depends on how much memory you need for the operating system plus
>> other
>> stuff you may have on the server. 1GB is great but with a simple server
>> with just SQL Server and SQL Agent running 512 will be fine. Using only
>> /3GB is simple and works you could combine them and allow for 3GB of
>> linear
>> memory and 500MB for AWE.
>> The configure value for memory is in MB so an int is plenty big enough.
>> See
>> BOL for details.
>> "Miles Obrien" <Miles Obrien@.discussions.microsoft.com> wrote in message
>> news:E1F0F023-61D5-4DC2-BD9F-C511570E371A@.microsoft.com...
>> >I have SQL Server2000 Ent. sitting on Win2003 Ent. with 4GB RAM.
>> >
>> > What are my options to best use the RAM?
>> > 1. /3GB in Boot.ini and AWE not enabled
>> > 2. /3GB in Boot.ini and AWE enabled.
>> >
>> > If AWE is not enabled and I have 4GB with /3GB in boot.ini, do I STILL
>> > need
>> > to set the MAX SERVER MEMORY to 3GB? If so, I cannot, since the MAX
>> > SERVER
>> > MEMORY datatype is INT and can only take 2GB
>> >
>> > Can anyone advise
>>|||Darn!
Was thinking the MAX SERVER MEMORY was in bytes!!!
In that case will leave it as it's default!
Thks Guys!
"Dan Guzman" wrote:
> > Actually all I wanted to know was, if I set /3GB and do not want to turn
> > on
> > AWE, how do I set the MAX SERVER MEMORY to 3GB when it has a datatype of
> > INT?
> The 'max server memory' specification is in MB. 3 GB = 3072 MB.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Miles Obrien" <MilesObrien@.discussions.microsoft.com> wrote in message
> news:47EAA1B3-82F1-4091-AC58-A08EF90BAD90@.microsoft.com...
> > Thks Danny.
> >
> > Actually all I wanted to know was, if I set /3GB and do not want to turn
> > on
> > AWE, how do I set the MAX SERVER MEMORY to 3GB when it has a datatype of
> > INT?
> >
> > Or - with AWE disabled and /3GB in Boot.ini how do I know SQL SERVER (or
> > tell it to) use 3GB of RAM?
> >
> > "Danny" wrote:
> >
> >> It depends on how much memory you need for the operating system plus
> >> other
> >> stuff you may have on the server. 1GB is great but with a simple server
> >> with just SQL Server and SQL Agent running 512 will be fine. Using only
> >> /3GB is simple and works you could combine them and allow for 3GB of
> >> linear
> >> memory and 500MB for AWE.
> >>
> >> The configure value for memory is in MB so an int is plenty big enough.
> >> See
> >> BOL for details.
> >>
> >> "Miles Obrien" <Miles Obrien@.discussions.microsoft.com> wrote in message
> >> news:E1F0F023-61D5-4DC2-BD9F-C511570E371A@.microsoft.com...
> >> >I have SQL Server2000 Ent. sitting on Win2003 Ent. with 4GB RAM.
> >> >
> >> > What are my options to best use the RAM?
> >> > 1. /3GB in Boot.ini and AWE not enabled
> >> > 2. /3GB in Boot.ini and AWE enabled.
> >> >
> >> > If AWE is not enabled and I have 4GB with /3GB in boot.ini, do I STILL
> >> > need
> >> > to set the MAX SERVER MEMORY to 3GB? If so, I cannot, since the MAX
> >> > SERVER
> >> > MEMORY datatype is INT and can only take 2GB
> >> >
> >> > Can anyone advise
> >>
> >>
> >>
>
>

/3GB

I've been doing some research on whether or not to use the /3GB switch, and
/PAE, in boot.ini but seem that I find contradicting information.
This article by Brian Moran seems to indicate I should use it, and I have
the utmost respect for Brian.
http://www.sqlmag.com/Article/ArticleID/45156/Using_SQL_Server_with_Large_Amounts_of_Memory.html
But I seem to see other articles by MS that either caution against it, or
say it should only be used with certain flavors or OS. And I can't even
find my OS in any of the articles.
I'm using Windows 2003 R2, SQL 2k sp4, on a Proliant 580 with 4GB of ram.
My box is a dedicated SQL Server. I am, temporarily, running IIS and
Reporting Services on the same box. Those will be offloaded to another
server shortly.
Can anyone tell me conclusively whether or not I should use the /3GB switch?
Thanks, AndreUse the /3GB, but don't use the /PAE. Reevaluate after you move IIS and SSRS
off of the box.
Since SQL 2000 can't access memory over 3GB without /PAE, and since /PEA
requires a large memory block (up to 1GB) just to manage memory, in your
scenario, you may actually be causing a reduction to the memory available to
SQL Server.
Configuration -Enabling AWE Memory for SQL Server
http://msdn2.microsoft.com/en-us/library/ms190673.aspx
Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Andre" <no@.spam.com> wrote in message
news:%23DJkotWFHHA.1252@.TK2MSFTNGP02.phx.gbl...
> I've been doing some research on whether or not to use the /3GB switch,
> and /PAE, in boot.ini but seem that I find contradicting information.
> This article by Brian Moran seems to indicate I should use it, and I have
> the utmost respect for Brian.
> http://www.sqlmag.com/Article/ArticleID/45156/Using_SQL_Server_with_Large_Amounts_of_Memory.html
> But I seem to see other articles by MS that either caution against it, or
> say it should only be used with certain flavors or OS. And I can't even
> find my OS in any of the articles.
> I'm using Windows 2003 R2, SQL 2k sp4, on a Proliant 580 with 4GB of ram.
> My box is a dedicated SQL Server. I am, temporarily, running IIS and
> Reporting Services on the same box. Those will be offloaded to another
> server shortly.
> Can anyone tell me conclusively whether or not I should use the /3GB
> switch?
> Thanks, Andre
>

/3gb

/3GB

I've been doing some research on whether or not to use the /3GB switch, and
/PAE, in boot.ini but seem that I find contradicting information.
This article by Brian Moran seems to indicate I should use it, and I have
the utmost respect for Brian.
[url]http://www.sqlmag.com/Article/ArticleID/45156/Using_SQL_Server_with_Large_Amounts_of_Memory.html [/url]
But I seem to see other articles by MS that either caution against it, or
say it should only be used with certain flavors or OS. And I can't even
find my OS in any of the articles.
I'm using Windows 2003 R2, SQL 2k sp4, on a Proliant 580 with 4GB of ram.
My box is a dedicated SQL Server. I am, temporarily, running IIS and
Reporting Services on the same box. Those will be offloaded to another
server shortly.
Can anyone tell me conclusively whether or not I should use the /3GB switch?
Thanks, Andre
Use the /3GB, but don't use the /PAE. Reevaluate after you move IIS and SSRS
off of the box.
Since SQL 2000 can't access memory over 3GB without /PAE, and since /PEA
requires a large memory block (up to 1GB) just to manage memory, in your
scenario, you may actually be causing a reduction to the memory available to
SQL Server.
Configuration -Enabling AWE Memory for SQL Server
http://msdn2.microsoft.com/en-us/library/ms190673.aspx
Configuration -Enabling Memory Support for Over 4 GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Andre" <no@.spam.com> wrote in message
news:%23DJkotWFHHA.1252@.TK2MSFTNGP02.phx.gbl...
> I've been doing some research on whether or not to use the /3GB switch,
> and /PAE, in boot.ini but seem that I find contradicting information.
> This article by Brian Moran seems to indicate I should use it, and I have
> the utmost respect for Brian.
> [url]http://www.sqlmag.com/Article/ArticleID/45156/Using_SQL_Server_with_Large_Amounts_of_Memory.html [/url]
> But I seem to see other articles by MS that either caution against it, or
> say it should only be used with certain flavors or OS. And I can't even
> find my OS in any of the articles.
> I'm using Windows 2003 R2, SQL 2k sp4, on a Proliant 580 with 4GB of ram.
> My box is a dedicated SQL Server. I am, temporarily, running IIS and
> Reporting Services on the same box. Those will be offloaded to another
> server shortly.
> Can anyone tell me conclusively whether or not I should use the /3GB
> switch?
> Thanks, Andre
>

/3G question

We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition. 8G
total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
enabled, and max server memeory configured to be 7G. From Task manager,
memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
server memory both show 7G.
My question is, without /3G, how could SQL use more than 6G of memory? Am I
missing something here? and most importantly, is there any performance
implications configuring SQL to use 7G without /3G boot option?
Thanks very much.
Brian
AWE enables SQL Server (or any properly enabled app) to see up to 64GB of
memory with the proper OS and SQL Editions. The /3GB has nothing to do with
AWE (other than you should turn it off at 12GB or higher to ensure enough
PTEs). It only allows the app to see 3GB instead of 2GB of directly
addressable memory.
http://sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk
Memory
http://www.sql-server-performance.com/awe_memory.asp Using AWE Memory
http://www.support.microsoft.com/?id=321363 SQL Server 7 & 2000 memory
usage
http://www.support.microsoft.com/?id=274750 Memory config
http://www.support.microsoft.com/?id=283037 Large Memory Support Is
Available in Windows 2000 (AWE)
http://www.support.microsoft.com/?id=811891 Can not use more than 2GB of
memory
Andrew J. Kelly SQL MVP
"Brian Brian" <BrianBrian@.discussions.microsoft.com> wrote in message
news:2DB937E4-6853-4EFB-B1F3-C23012F70734@.microsoft.com...
> We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition.
> 8G
> total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
> enabled, and max server memeory configured to be 7G. From Task manager,
> memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
> server memory both show 7G.
> My question is, without /3G, how could SQL use more than 6G of memory? Am
> I
> missing something here? and most importantly, is there any performance
> implications configuring SQL to use 7G without /3G boot option?
> Thanks very much.
> --
> Brian
|||Hi Brian
I'm not sure where you get the 6GB figure from. Without AWE, SQL Server is
limited to either 2GB or 3GB. With AWE, SQL Server can use up to 64GB,
depending on the version and edition. The /3GB switch only controls how
much memory is directly addressable. All memory above 2GB or 3GB must be
accessed through AWE memory mapping.
Direct addressing is slightly faster than going through AWE, so with the 3GB
flag you will get to more memory slightly faster. In addition, only pages
from your data files can use the memory addressed through AWE. All other
memory uses (query plan, user connections, lock memory, etc) has to use
directly addressed memory, so having 3GB enabled will give you up to 50%
more space for those other memory uses. This can be a good thing.
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"Brian Brian" <BrianBrian@.discussions.microsoft.com> wrote in message
news:2DB937E4-6853-4EFB-B1F3-C23012F70734@.microsoft.com...
> We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition.
> 8G
> total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
> enabled, and max server memeory configured to be 7G. From Task manager,
> memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
> server memory both show 7G.
> My question is, without /3G, how could SQL use more than 6G of memory? Am
> I
> missing something here? and most importantly, is there any performance
> implications configuring SQL to use 7G without /3G boot option?
> Thanks very much.
> --
> Brian

/3G question

We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition. 8G
total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
enabled, and max server memeory configured to be 7G. From Task manager,
memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
server memory both show 7G.
My question is, without /3G, how could SQL use more than 6G of memory? Am I
missing something here? and most importantly, is there any performance
implications configuring SQL to use 7G without /3G boot option?
Thanks very much.
--
BrianAWE enables SQL Server (or any properly enabled app) to see up to 64GB of
memory with the proper OS and SQL Editions. The /3GB has nothing to do with
AWE (other than you should turn it off at 12GB or higher to ensure enough
PTEs). It only allows the app to see 3GB instead of 2GB of directly
addressable memory.
http://sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk
Memory
http://www.sql-server-performance.com/awe_memory.asp Using AWE Memory
http://www.support.microsoft.com/?id=321363 SQL Server 7 & 2000 memory
usage
http://www.support.microsoft.com/?id=274750 Memory config
http://www.support.microsoft.com/?id=283037 Large Memory Support Is
Available in Windows 2000 (AWE)
http://www.support.microsoft.com/?id=811891 Can not use more than 2GB of
memory
--
Andrew J. Kelly SQL MVP
"Brian Brian" <BrianBrian@.discussions.microsoft.com> wrote in message
news:2DB937E4-6853-4EFB-B1F3-C23012F70734@.microsoft.com...
> We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition.
> 8G
> total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
> enabled, and max server memeory configured to be 7G. From Task manager,
> memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
> server memory both show 7G.
> My question is, without /3G, how could SQL use more than 6G of memory? Am
> I
> missing something here? and most importantly, is there any performance
> implications configuring SQL to use 7G without /3G boot option?
> Thanks very much.
> --
> Brian|||Hi Brian
I'm not sure where you get the 6GB figure from. Without AWE, SQL Server is
limited to either 2GB or 3GB. With AWE, SQL Server can use up to 64GB,
depending on the version and edition. The /3GB switch only controls how
much memory is directly addressable. All memory above 2GB or 3GB must be
accessed through AWE memory mapping.
Direct addressing is slightly faster than going through AWE, so with the 3GB
flag you will get to more memory slightly faster. In addition, only pages
from your data files can use the memory addressed through AWE. All other
memory uses (query plan, user connections, lock memory, etc) has to use
directly addressed memory, so having 3GB enabled will give you up to 50%
more space for those other memory uses. This can be a good thing.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"Brian Brian" <BrianBrian@.discussions.microsoft.com> wrote in message
news:2DB937E4-6853-4EFB-B1F3-C23012F70734@.microsoft.com...
> We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition.
> 8G
> total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
> enabled, and max server memeory configured to be 7G. From Task manager,
> memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
> server memory both show 7G.
> My question is, without /3G, how could SQL use more than 6G of memory? Am
> I
> missing something here? and most importantly, is there any performance
> implications configuring SQL to use 7G without /3G boot option?
> Thanks very much.
> --
> Brian

/3G question

We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition. 8G
total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
enabled, and max server memeory configured to be 7G. From Task manager,
memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
server memory both show 7G.
My question is, without /3G, how could SQL use more than 6G of memory? Am I
missing something here? and most importantly, is there any performance
implications configuring SQL to use 7G without /3G boot option?
Thanks very much.
--
BrianAWE enables SQL Server (or any properly enabled app) to see up to 64GB of
memory with the proper OS and SQL Editions. The /3GB has nothing to do with
AWE (other than you should turn it off at 12GB or higher to ensure enough
PTEs). It only allows the app to see 3GB instead of 2GB of directly
addressable memory.
http://sqljunkies.com/Tutorial/0D4F...F2FE2D58F6.scuk
Memory
http://www.sql-server-performance.com/awe_memory.asp Using AWE Memory
http://www.support.microsoft.com/?id=321363 SQL Server 7 & 2000 memory
usage
http://www.support.microsoft.com/?id=274750 Memory config
http://www.support.microsoft.com/?id=283037 Large Memory Support Is
Available in Windows 2000 (AWE)
http://www.support.microsoft.com/?id=811891 Can not use more than 2GB of
memory
Andrew J. Kelly SQL MVP
"Brian Brian" <BrianBrian@.discussions.microsoft.com> wrote in message
news:2DB937E4-6853-4EFB-B1F3-C23012F70734@.microsoft.com...
> We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition.
> 8G
> total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
> enabled, and max server memeory configured to be 7G. From Task manager,
> memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
> server memory both show 7G.
> My question is, without /3G, how could SQL use more than 6G of memory? Am
> I
> missing something here? and most importantly, is there any performance
> implications configuring SQL to use 7G without /3G boot option?
> Thanks very much.
> --
> Brian|||Hi Brian
I'm not sure where you get the 6GB figure from. Without AWE, SQL Server is
limited to either 2GB or 3GB. With AWE, SQL Server can use up to 64GB,
depending on the version and edition. The /3GB switch only controls how
much memory is directly addressable. All memory above 2GB or 3GB must be
accessed through AWE memory mapping.
Direct addressing is slightly faster than going through AWE, so with the 3GB
flag you will get to more memory slightly faster. In addition, only pages
from your data files can use the memory addressed through AWE. All other
memory uses (query plan, user connections, lock memory, etc) has to use
directly addressed memory, so having 3GB enabled will give you up to 50%
more space for those other memory uses. This can be a good thing.
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"Brian Brian" <BrianBrian@.discussions.microsoft.com> wrote in message
news:2DB937E4-6853-4EFB-B1F3-C23012F70734@.microsoft.com...
> We have some boxes with Sql 2000 sp4 on windows 2003 enterprise edition.
> 8G
> total physical memory, boot.ini options with /PAE but without /3G. SQL AWE
> enabled, and max server memeory configured to be 7G. From Task manager,
> memory utilization is 7.2G. From perf mon, sql target mem is 7G and total
> server memory both show 7G.
> My question is, without /3G, how could SQL use more than 6G of memory? Am
> I
> missing something here? and most importantly, is there any performance
> implications configuring SQL to use 7G without /3G boot option?
> Thanks very much.
> --
> Brian

Tuesday, March 20, 2012

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

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

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

Monday, March 19, 2012

/3GB benifits

/3GB and Maximum server memory

/3GB and Maximum server memory

/3GB

/3gb

/3gb

/3GB

/3gb

/3GB

/3G question

/3G question

/3G question

SQL SQLExpress

Blog Archive

About Me