Showing posts with label awe. Show all posts
Showing posts with label awe. Show all posts

Friday, March 30, 2012

PAE VS SQL Server AWE

Hi,
I have set the boot.ini /PAE and 3GB Parameters in my windows 2003 server
enterprise.
And SQL Server 2000 also open AWE's "Max Server Memory" as 6G (I have 8G
physical memory).
So, these 2 options -- boot.ini 3GB parameter and the "Max Server Memroy" of
SQL Server 2000 as 6G can use at the same time?
If can't, what's problem will happen?
Thanks!
AngiThis should be fine.
Problems can occur if you use /3GB when you have over 12GB of Memory,
although some people say you can go up to 16GB. You'd have to test it on
your system. But 6GB should be fine.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"angi" <enchiw@.msn.com> wrote in message
news:ezI0joVFFHA.3728@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have set the boot.ini /PAE and 3GB Parameters in my windows 2003 server
> enterprise.
> And SQL Server 2000 also open AWE's "Max Server Memory" as 6G (I have 8G
> physical memory).
> So, these 2 options -- boot.ini 3GB parameter and the "Max Server Memroy"
> of
> SQL Server 2000 as 6G can use at the same time?
> If can't, what's problem will happen?
> Thanks!
> Angi
>
>|||This is a multi-part message in MIME format.
--080509010402010100010709
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Ken Henderson from Microsoft (is he still there?) says in _The Guru's
Guide to SQL Server Architecture and Internals_ (awesome book - right up
there with _Inside SQL Server 2000, Second Edition_ by someone named
Kalen Delaney :-P ) that when you shrink the kernel mode address space
from 2GB to 1GB (with /3GB) one of the main things that suffers is "the
table Windows uses to manage the physical memory...such that it can
manage a maximum of only 16GB of physical memory." Is that right or is
12GB the magic figure?
--
*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
Kalen Delaney wrote:
>This should be fine.
>Problems can occur if you use /3GB when you have over 12GB of Memory,
>although some people say you can go up to 16GB. You'd have to test it on
>your system. But 6GB should be fine.
>
>
--080509010402010100010709
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>Ken Henderson from Microsoft (is he still there?) says in <u>The
Guru's Guide to SQL Server Architecture and Internals</u> (awesome book
- right up there with <u>Inside SQL Server 2000, Second Edition</u> by
someone named Kalen Delaney <span class="moz-smiley-s4"><span> :-P </span></span>
) that when you shrink the kernel mode address space from 2GB to 1GB
(with /3GB) one of the main things that suffers is "the table Windows
uses to manage the physical memory...such that it can manage a maximum
of only 16GB of physical memory." Is that right or is 12GB the magic
figure?</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Kalen Delaney wrote:
<blockquote cite="mid%2336sKXXFFHA.3728@.TK2MSFTNGP14.phx.gbl"
type="cite">
<pre wrap="">This should be fine.
Problems can occur if you use /3GB when you have over 12GB of Memory,
although some people say you can go up to 16GB. You'd have to test it on
your system. But 6GB should be fine.
</pre>
</blockquote>
</body>
</html>
--080509010402010100010709--|||Hi
Officially, from MS, 16GB is the number, but some hardware vendors (they
might produce ES 7000's) have recommended to customers to use a maximum of
12GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:unS1eUYFFHA.1264@.TK2MSFTNGP12.phx.gbl...
> Ken Henderson from Microsoft (is he still there?) says in _The Guru's
> Guide to SQL Server Architecture and Internals_ (awesome book - right up
> there with _Inside SQL Server 2000, Second Edition_ by someone named
> Kalen Delaney :-P ) that when you shrink the kernel mode address space
> from 2GB to 1GB (with /3GB) one of the main things that suffers is "the
> table Windows uses to manage the physical memory...such that it can
> manage a maximum of only 16GB of physical memory." Is that right or is
> 12GB the magic figure?
> --
> *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
>
> Kalen Delaney wrote:
> >This should be fine.
> >Problems can occur if you use /3GB when you have over 12GB of Memory,
> >although some people say you can go up to 16GB. You'd have to test it on
> >your system. But 6GB should be fine.
> >
> >
> >
>|||Yes, this is exactly what I wasa referring to.
That fact that YMMV.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OxsVjraFFHA.3928@.TK2MSFTNGP15.phx.gbl...
> Hi
> Officially, from MS, 16GB is the number, but some hardware vendors (they
> might produce ES 7000's) have recommended to customers to use a maximum of
> 12GB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
> news:unS1eUYFFHA.1264@.TK2MSFTNGP12.phx.gbl...
>> Ken Henderson from Microsoft (is he still there?) says in _The Guru's
>> Guide to SQL Server Architecture and Internals_ (awesome book - right up
>> there with _Inside SQL Server 2000, Second Edition_ by someone named
>> Kalen Delaney :-P ) that when you shrink the kernel mode address space
>> from 2GB to 1GB (with /3GB) one of the main things that suffers is "the
>> table Windows uses to manage the physical memory...such that it can
>> manage a maximum of only 16GB of physical memory." Is that right or is
>> 12GB the magic figure?
>> --
>> *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
>>
>> Kalen Delaney wrote:
>> >This should be fine.
>> >Problems can occur if you use /3GB when you have over 12GB of Memory,
>> >although some people say you can go up to 16GB. You'd have to test it on
>> >your system. But 6GB should be fine.
>> >
>> >
>> >
>

PAE VS SQL Server AWE

Hi,
I have set the boot.ini /PAE and 3GB Parameters in my windows 2003 server
enterprise.
And SQL Server 2000 also open AWE's "Max Server Memory" as 6G (I have 8G
physical memory).
So, these 2 options -- boot.ini 3GB parameter and the "Max Server Memroy" of
SQL Server 2000 as 6G can use at the same time?
If can't, what's problem will happen?
Thanks!
AngiThis should be fine.
Problems can occur if you use /3GB when you have over 12GB of Memory,
although some people say you can go up to 16GB. You'd have to test it on
your system. But 6GB should be fine.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"angi" <enchiw@.msn.com> wrote in message
news:ezI0joVFFHA.3728@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have set the boot.ini /PAE and 3GB Parameters in my windows 2003 server
> enterprise.
> And SQL Server 2000 also open AWE's "Max Server Memory" as 6G (I have 8G
> physical memory).
> So, these 2 options -- boot.ini 3GB parameter and the "Max Server Memroy"
> of
> SQL Server 2000 as 6G can use at the same time?
> If can't, what's problem will happen?
> Thanks!
> Angi
>
>|||Ken Henderson from Microsoft (is he still there?) says in _The Guru's
Guide to SQL Server Architecture and Internals_ (awesome book - right up
there with _Inside SQL Server 2000, Second Edition_ by someone named
Kalen Delaney :-P ) that when you shrink the kernel mode address space
from 2GB to 1GB (with /3GB) one of the main things that suffers is "the
table Windows uses to manage the physical memory...such that it can
manage a maximum of only 16GB of physical memory." Is that right or is
12GB the magic figure?
*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
Kalen Delaney wrote:

>This should be fine.
>Problems can occur if you use /3GB when you have over 12GB of Memory,
>although some people say you can go up to 16GB. You'd have to test it on
>your system. But 6GB should be fine.
>
>|||Hi
Officially, from MS, 16GB is the number, but some hardware vendors (they
might produce ES 7000's) have recommended to customers to use a maximum of
12GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:unS1eUYFFHA.1264@.TK2MSFTNGP12.phx.gbl...
> Ken Henderson from Microsoft (is he still there?) says in _The Guru's
> Guide to SQL Server Architecture and Internals_ (awesome book - right up
> there with _Inside SQL Server 2000, Second Edition_ by someone named
> Kalen Delaney :-P ) that when you shrink the kernel mode address space
> from 2GB to 1GB (with /3GB) one of the main things that suffers is "the
> table Windows uses to manage the physical memory...such that it can
> manage a maximum of only 16GB of physical memory." Is that right or is
> 12GB the magic figure?
> --
> *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
>
> Kalen Delaney wrote:
>
>|||Yes, this is exactly what I wasa referring to.
That fact that YMMV.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OxsVjraFFHA.3928@.TK2MSFTNGP15.phx.gbl...
> Hi
> Officially, from MS, 16GB is the number, but some hardware vendors (they
> might produce ES 7000's) have recommended to customers to use a maximum of
> 12GB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
> news:unS1eUYFFHA.1264@.TK2MSFTNGP12.phx.gbl...
> http://www.mallesons.com
>

PAE VS SQL Server AWE

Hi,
I have set the boot.ini /PAE and 3GB Parameters in my windows 2003 server
enterprise.
And SQL Server 2000 also open AWE's "Max Server Memory" as 6G (I have 8G
physical memory).
So, these 2 options -- boot.ini 3GB parameter and the "Max Server Memroy" of
SQL Server 2000 as 6G can use at the same time?
If can't, what's problem will happen?
Thanks!
Angi
This should be fine.
Problems can occur if you use /3GB when you have over 12GB of Memory,
although some people say you can go up to 16GB. You'd have to test it on
your system. But 6GB should be fine.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"angi" <enchiw@.msn.com> wrote in message
news:ezI0joVFFHA.3728@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have set the boot.ini /PAE and 3GB Parameters in my windows 2003 server
> enterprise.
> And SQL Server 2000 also open AWE's "Max Server Memory" as 6G (I have 8G
> physical memory).
> So, these 2 options -- boot.ini 3GB parameter and the "Max Server Memroy"
> of
> SQL Server 2000 as 6G can use at the same time?
> If can't, what's problem will happen?
> Thanks!
> Angi
>
>
|||Ken Henderson from Microsoft (is he still there?) says in _The Guru's
Guide to SQL Server Architecture and Internals_ (awesome book - right up
there with _Inside SQL Server 2000, Second Edition_ by someone named
Kalen Delaney :-P ) that when you shrink the kernel mode address space
from 2GB to 1GB (with /3GB) one of the main things that suffers is "the
table Windows uses to manage the physical memory...such that it can
manage a maximum of only 16GB of physical memory." Is that right or is
12GB the magic figure?
*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
Kalen Delaney wrote:

>This should be fine.
>Problems can occur if you use /3GB when you have over 12GB of Memory,
>although some people say you can go up to 16GB. You'd have to test it on
>your system. But 6GB should be fine.
>
>
|||Hi
Officially, from MS, 16GB is the number, but some hardware vendors (they
might produce ES 7000's) have recommended to customers to use a maximum of
12GB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:unS1eUYFFHA.1264@.TK2MSFTNGP12.phx.gbl...
> Ken Henderson from Microsoft (is he still there?) says in _The Guru's
> Guide to SQL Server Architecture and Internals_ (awesome book - right up
> there with _Inside SQL Server 2000, Second Edition_ by someone named
> Kalen Delaney :-P ) that when you shrink the kernel mode address space
> from 2GB to 1GB (with /3GB) one of the main things that suffers is "the
> table Windows uses to manage the physical memory...such that it can
> manage a maximum of only 16GB of physical memory." Is that right or is
> 12GB the magic figure?
> --
> *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
>
> Kalen Delaney wrote:
>
|||Yes, this is exactly what I wasa referring to.
That fact that YMMV.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OxsVjraFFHA.3928@.TK2MSFTNGP15.phx.gbl...
> Hi
> Officially, from MS, 16GB is the number, but some hardware vendors (they
> might produce ES 7000's) have recommended to customers to use a maximum of
> 12GB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
> news:unS1eUYFFHA.1264@.TK2MSFTNGP12.phx.gbl...
> http://www.mallesons.com
>
sql

PAE & AWE Question

Hello:
I am evaluating performance issues on a SQL server and trying to understand
when to use the PAE switch.
I have a Windows 2000 Advanced server SP4 running MS SQL Server Enterprise
Edition SP4. The server has 4GB total physical RAM. Do I need to configure
PAE/AWE for SQL to take advantage of more than 2GB of RAM?
SQL services fail at times due to high memory utilization. Any assistance
would be appreciated!
Thanks,
WHello,
If your server has only 4GB of memory you can not use AWE. By default
Windows uses 2 GB and SQL Server can use the remaining 2 GB. By adding the
/3GB switch to the Windows boot.ini file you can have Windows to use only 1
GB so SQL Server can use the remaining 3 GB.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Walid" wrote:
> Hello:
> I am evaluating performance issues on a SQL server and trying to understand
> when to use the PAE switch.
> I have a Windows 2000 Advanced server SP4 running MS SQL Server Enterprise
> Edition SP4. The server has 4GB total physical RAM. Do I need to configure
> PAE/AWE for SQL to take advantage of more than 2GB of RAM?
> SQL services fail at times due to high memory utilization. Any assistance
> would be appreciated!
> Thanks,
> W|||If you visit the following link, you'll understand PAE better.
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
And for AWE, PAE, 3GB:
http://support.microsoft.com/kb/274750/en-us
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:350CF984-8737-43F6-8570-189A7C81AFFD@.microsoft.com...
> Hello:
> I am evaluating performance issues on a SQL server and trying to
> understand
> when to use the PAE switch.
> I have a Windows 2000 Advanced server SP4 running MS SQL Server Enterprise
> Edition SP4. The server has 4GB total physical RAM. Do I need to
> configure
> PAE/AWE for SQL to take advantage of more than 2GB of RAM?
> SQL services fail at times due to high memory utilization. Any assistance
> would be appreciated!
> Thanks,
> W|||Thank you all very much for the info!!
"Ekrem Ã?nsoy" wrote:
> If you visit the following link, you'll understand PAE better.
> http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
> And for AWE, PAE, 3GB:
> http://support.microsoft.com/kb/274750/en-us
> --
> Ekrem Ã?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:350CF984-8737-43F6-8570-189A7C81AFFD@.microsoft.com...
> > Hello:
> > I am evaluating performance issues on a SQL server and trying to
> > understand
> > when to use the PAE switch.
> >
> > I have a Windows 2000 Advanced server SP4 running MS SQL Server Enterprise
> > Edition SP4. The server has 4GB total physical RAM. Do I need to
> > configure
> > PAE/AWE for SQL to take advantage of more than 2GB of RAM?
> >
> > SQL services fail at times due to high memory utilization. Any assistance
> > would be appreciated!
> >
> > Thanks,
> >
> > W
>|||> If your server has only 4GB of memory you can not use AWE.
Not true. See
http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
Linchi
"Ben Nevarez" wrote:
> Hello,
> If your server has only 4GB of memory you can not use AWE. By default
> Windows uses 2 GB and SQL Server can use the remaining 2 GB. By adding the
> /3GB switch to the Windows boot.ini file you can have Windows to use only 1
> GB so SQL Server can use the remaining 3 GB.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Walid" wrote:
> > Hello:
> > I am evaluating performance issues on a SQL server and trying to understand
> > when to use the PAE switch.
> >
> > I have a Windows 2000 Advanced server SP4 running MS SQL Server Enterprise
> > Edition SP4. The server has 4GB total physical RAM. Do I need to configure
> > PAE/AWE for SQL to take advantage of more than 2GB of RAM?
> >
> > SQL services fail at times due to high memory utilization. Any assistance
> > would be appreciated!
> >
> > Thanks,
> >
> > W|||Again, a nice work by Linchi... Thanks.
--
Ekrem Ã?nsoy
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:10FB2A3A-4BA1-4118-B376-D65B96BEB5D7@.microsoft.com...
>> If your server has only 4GB of memory you can not use AWE.
> Not true. See
> http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
> Linchi
> "Ben Nevarez" wrote:
>> Hello,
>> If your server has only 4GB of memory you can not use AWE. By default
>> Windows uses 2 GB and SQL Server can use the remaining 2 GB. By adding
>> the
>> /3GB switch to the Windows boot.ini file you can have Windows to use only
>> 1
>> GB so SQL Server can use the remaining 3 GB.
>> Hope this helps,
>> Ben Nevarez
>> Senior Database Administrator
>> AIG SunAmerica
>>
>> "Walid" wrote:
>> > Hello:
>> > I am evaluating performance issues on a SQL server and trying to
>> > understand
>> > when to use the PAE switch.
>> >
>> > I have a Windows 2000 Advanced server SP4 running MS SQL Server
>> > Enterprise
>> > Edition SP4. The server has 4GB total physical RAM. Do I need to
>> > configure
>> > PAE/AWE for SQL to take advantage of more than 2GB of RAM?
>> >
>> > SQL services fail at times due to high memory utilization. Any
>> > assistance
>> > would be appreciated!
>> >
>> > Thanks,
>> >
>> > W

PAE & AWE on x64 Windows & SQL

We've just setup some new Microsoft SQL 2005 servers running windows 2003 R2
x64 with 16GB of RAM. Since we are running a 64 bit version of windows and a
64 bit version of SQL, is it any longer neccesary to add the /3GB /PAE
option in the boot.ini and enable AWE in SQL?
Thanks!
Brad"Brad Baker" <brad@.nospam.nospam> wrote in message
news:OF%23WZo3xGHA.2384@.TK2MSFTNGP05.phx.gbl...
> We've just setup some new Microsoft SQL 2005 servers running windows 2003
> R2 x64 with 16GB of RAM. Since we are running a 64 bit version of windows
> and a 64 bit version of SQL, is it any longer neccesary to add the /3GB
> /PAE option in the boot.ini and enable AWE in SQL?
>
Slava says no /3GB, no /PAE, no AWE option. Just grant the SQL account the
"Lock Pages in Memory" privilege.
Q and A: Using Lock Pages In memory on 64 bit platform
Q: Hello Slava, I would like to confirm my understanding that on SQL 2005
64 bit edition it is recommended to grant Lock Pages in Memory right to the
SQL account and then turn on the AWE setting. Thanks
A: Yes, we do recommend to turn on Lock pages in memory so that OS doesn't
page SQL Server out. However on 64 bit you only need to grant the right
"Lock Pages in Memory" to the SQL account for SQL Server to utilize this
feature. You do need to to change any of AWE settings through sp_configure.
http://blogs.msdn.com/slavao/archive/2005/08/31/458545.aspx
Slava explains:
http://blogs.msdn.com/slavao/archive/2005/04/29/413425.aspx
David

PAE & AWE on x64 Windows & SQL

We've just setup some new Microsoft SQL 2005 servers running windows 2003 R2
x64 with 16GB of RAM. Since we are running a 64 bit version of windows and a
64 bit version of SQL, is it any longer neccesary to add the /3GB /PAE
option in the boot.ini and enable AWE in SQL?
Thanks!
Brad"Brad Baker" <brad@.nospam.nospam> wrote in message
news:OF%23WZo3xGHA.2384@.TK2MSFTNGP05.phx.gbl...
> We've just setup some new Microsoft SQL 2005 servers running windows 2003
> R2 x64 with 16GB of RAM. Since we are running a 64 bit version of windows
> and a 64 bit version of SQL, is it any longer neccesary to add the /3GB
> /PAE option in the boot.ini and enable AWE in SQL?
>
Slava says no /3GB, no /PAE, no AWE option. Just grant the SQL account the
"Lock Pages in Memory" privilege.
Q and A: Using Lock Pages In memory on 64 bit platform
Q: Hello Slava, I would like to confirm my understanding that on SQL 2005
64 bit edition it is recommended to grant Lock Pages in Memory right to the
SQL account and then turn on the AWE setting. Thanks
A: Yes, we do recommend to turn on Lock pages in memory so that OS doesn't
page SQL Server out. However on 64 bit you only need to grant the right
"Lock Pages in Memory" to the SQL account for SQL Server to utilize this
feature. You do need to to change any of AWE settings through sp_configure.
http://blogs.msdn.com/slavao/archiv.../31/458545.aspx
Slava explains:
http://blogs.msdn.com/slavao/archiv.../29/413425.aspx
David