sql overflow error: 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 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?</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>
 
 
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.
>> >
>> >
>> >
>

Friday, March 30, 2012

PAE VS SQL Server AWE

No comments:

Post a Comment

sql overflow error

Blog Archive

About Me