I have a pair of clustered sql server with 12GB of memory in each. What do
you recommend in allocating memory space? I was told to add a /3gb and /pae
switch is boot.ini. please let me know if this is best practice.
thanks!
--
Calvin
doc@.ebay.comsorry... forgot some details. both boxes are W2K3 enterprise with sql 2000
enterprise.
"Calvin Do" wrote:
> Hello,
> I have a pair of clustered sql server with 12GB of memory in each. What do
> you recommend in allocating memory space? I was told to add a /3gb and /pae
> switch is boot.ini. please let me know if this is best practice.
>
> thanks!
> --
> Calvin
> doc@.ebay.com|||This is a multi-part message in MIME format.
--=_NextPart_000_00DA_01C4AFDA.4AD438D0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Calvin,
Enabling /PAE will enable Windows address more than 4gb... good way of =making use of available RAM.
/3gb switch will make 3gb of virtual memory address space available to =Sql server for Buffer cache.
Turn on AWE for data-caching on your available physical memory.
All these are ways of allocating more memory for sql server use.
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;q321363
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/archit=
ec/8_ar_sa_6b3k.asp
Also refer to this earlier post below:
Definitely apply the hotfix mentioned for article 834628. Another DBA =here
ran into something that he thinks may have been caused by this issue.
Don't use /3GB when you have more than 12 GB of RAM in your system. =The OS
needs the extra mamory to handle mapping AWE memory back into the =lower 4GB
address space. Finally, set the MAX SERVER MEMORY to about 2-4GB less =than
your physical memory.
-- Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Larry Kippenhan" <lwkthrowaway1@.comcast.net> wrote in message
news:e$pzBY9rEHA.2128@.TK2MSFTNGP10.phx.gbl...
> I have a couple of questions that I hope y'all will be able to give =me
> some info on.
>
> I am installing SQL Server 2000 on a Win2K3 Enterprise server with =20GB
> of RAM (I know, odd number), anyway, as I was searching for =information
> on enabling all of my memory, and the /PAE option, I came across a =KB
> article, #834628
> (http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;834628), =titled
> "Data is corrupted when PAE is enabled on a Windows Server =2003-based
> computer". I expect this machine to give the resources a pretty =good
> workout, and I was concerned about running into this issue. Has any =of
> you run into this issue? Or, how likely is it that I will =experience
> this. Microsoft suggests not installing the hotfix unless you are
> severely affected by this bug. To me, ANY corruption counts as =severe,
> and I really don't want to have to do all of the restores, and send =400
> people home, etc, etc, while I fix this thing. So, any info here is
> appreciated.
>
> Second question I had was: with the /PAE option, and awe enabled on =the
> SQL Server, it consumed as much of the available memory as it could
> (about 19.7 GB). This in itself doesn't bother me, but what had me
> puzzled, was that it appeared to be using the memory that was below =the
> 4GB line. I really expected that it wouldn't since I hadn't used =the
> /3GB switch. Any thoughts on this? Is /3GB not needed anymore, or =is
> my understanding not in line with reality?
>
> Thanks again for your insights.
>
> Larry
--=_NextPart_000_00DA_01C4AFDA.4AD438D0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Calvin,
Enabling /PAE will enable Windows =address more than 4gb... good way of making use of available RAM.
/3gb switch will make 3gb of virtual =memory address space available to Sql server for Buffer cache.
Turn on AWE for data-caching on your =available physical memory.
All these are ways of allocating more =memory for sql server use.
http://msdn.microsoft.com/library/default.as=p?url=3D/library/en-us/architec/8_ar_sa_6b3k.asp
Also refer to this earlier post below:
Definitely apply the hotfix mentioned for article 834628. Another DBA =hereran into something that he thinks may have been caused by this =issue.Don't use /3GB when you have more than 12 GB of RAM in your system. =The OSneeds the extra mamory to handle mapping AWE memory back into =the lower 4GBaddress space. Finally, set the MAX SERVER MEMORY to =about 2-4GB less thanyour physical memory.-- Geoff N. =HitenMicrosoft SQL Server MVPSenior Database =AdministratorCareerbuilder.comI support the Professional Association for SQL Serverhttp://www.sqlpass.org">www.sqlpass.org"Larry =Kippenhan"
--=_NextPart_000_00DA_01C4AFDA.4AD438D0--|||thanks, appreciate your response.
"TJ" wrote:
> Calvin,
> Enabling /PAE will enable Windows address more than 4gb... good way of making use of available RAM.
> /3gb switch will make 3gb of virtual memory address space available to Sql server for Buffer cache.
> Turn on AWE for data-caching on your available physical memory.
> All these are ways of allocating more memory for sql server use.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa_6b3k.asp
>
> Also refer to this earlier post below:
>
> Definitely apply the hotfix mentioned for article 834628. Another DBA here
> ran into something that he thinks may have been caused by this issue.
> Don't use /3GB when you have more than 12 GB of RAM in your system. The OS
> needs the extra mamory to handle mapping AWE memory back into the lower 4GB
> address space. Finally, set the MAX SERVER MEMORY to about 2-4GB less than
> your physical memory.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Larry Kippenhan" <lwkthrowaway1@.comcast.net> wrote in message
> news:e$pzBY9rEHA.2128@.TK2MSFTNGP10.phx.gbl...
> > I have a couple of questions that I hope y'all will be able to give me
> > some info on.
> >
> > I am installing SQL Server 2000 on a Win2K3 Enterprise server with 20GB
> > of RAM (I know, odd number), anyway, as I was searching for information
> > on enabling all of my memory, and the /PAE option, I came across a KB
> > article, #834628
> > (http://support.microsoft.com/default.aspx?scid=kb;en-us;834628), titled
> > "Data is corrupted when PAE is enabled on a Windows Server 2003-based
> > computer". I expect this machine to give the resources a pretty good
> > workout, and I was concerned about running into this issue. Has any of
> > you run into this issue? Or, how likely is it that I will experience
> > this. Microsoft suggests not installing the hotfix unless you are
> > severely affected by this bug. To me, ANY corruption counts as severe,
> > and I really don't want to have to do all of the restores, and send 400
> > people home, etc, etc, while I fix this thing. So, any info here is
> > appreciated.
> >
> > Second question I had was: with the /PAE option, and awe enabled on the
> > SQL Server, it consumed as much of the available memory as it could
> > (about 19.7 GB). This in itself doesn't bother me, but what had me
> > puzzled, was that it appeared to be using the memory that was below the
> > 4GB line. I really expected that it wouldn't since I hadn't used the
> > /3GB switch. Any thoughts on this? Is /3GB not needed anymore, or is
> > my understanding not in line with reality?
> >
> > Thanks again for your insights.
> >
> > Larry
>
No comments:
Post a Comment