Showing posts with label pae. Show all posts
Showing posts with label pae. 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 SQL server questions...

Hey all,

I'm wondering what command I could issue to see the amount of memory a named instance is using from within the instance itself. We've enabled address extensions (PAE), and task manager no longer shows the correct amount of mem being used by the process. Under perfmon, I've added the object MSSQL$INSTANCENAME:Memory and I'm looking at the Total Server Memory. I'm seeing 4 gigs, when max memory is capped at 2gigs. This must show the server memory and not the instance memory ? Is there some way to see the instance memory ?

Cheers,
-KilkaDBCC MEMORYSTATUS. It'll give you enough to start with. Coupled with MEMUSAGE, you can pi-point the exact object that hogs the memory.|||Thanks rdjabarov,

I'll have to check this out on our testing environments. I've read that MEMUSAGE can cause the instance to crash, I'll have to do some more testing when I get back to work to verify that it'll be safe to use on live.

Cheers,
-Kilka

PAE problem question (KB834628)

This question is related to
http://support.microsoft.com/defaul...b;en-us;834628.
We had a database crash about a month ago that was non-recoverable. This was
a subscriber database run in a continuous transactional environment. Server
is W2K3, /PAE and /3GB, 8GB ram, SQL Server gets 6655mb.
I ran a dbcc checkdb and came back with a large number of errors starting
with Errors 1 (see "Errors 1" below).
There are quite few more errors. The checkdb ends with
--CHECKDB found 0 allocation errors and 150 consistency errors in
database 'DB_rpt1'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (DB_rpt1 ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.--
---
At the time we saw absolutely no errors at ANY level (SAN, OS, etc) except
when the SQL Server errorlog start screaming about --
2004-02-18 16:48:32.10 spid52 Error: 823, Severity: 24, State: 2
2004-02-18 16:48:32.10 spid52 I/O error (bad page ID) detected during
read at offset 0x00000004a66000 in file
'w:\DBdata\DB_rpt1_data2.NDF'..--
We had an HBA hardware failure 6 days later, we semi-attributed the
corruption to the bad HBA.
Could this be the 834628 problem? If so how can I tell - the KB is fairly
non-specific about how to spot the error.
Also would the fn_dblog function be of any use and what would I look for -
the article seems to say that one line would be all zero's but this isn't
that clear.
---
Errors 1 --(this is the very beginning of the checkdb
dump)--
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9523). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9524). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9525). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9526). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9527). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9528). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9529). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (4:9530). The PageId in the
page header = (0:0).
DBCC results for 'DB_rpt1'.
CHECKDB found 0 allocation errors and 8 consistency errors not associated
with any single object.That is very unlikely a PAE problem. Errors like that are almost always
attributable to bad blocks on disk. With an HBA on the blink, it is likely
that some bad data got written to the disk array, possibly where data was
deleted since the pages are not owned by a specific object.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"frankm" <frank@.nxspxm.mallardcentral.com> wrote in message
news:uHA$AJOEEHA.3472@.TK2MSFTNGP09.phx.gbl...
> This question is related to
> http://support.microsoft.com/defaul...b;en-us;834628.
> We had a database crash about a month ago that was non-recoverable. This
was
> a subscriber database run in a continuous transactional environment.
Server
> is W2K3, /PAE and /3GB, 8GB ram, SQL Server gets 6655mb.
> I ran a dbcc checkdb and came back with a large number of errors starting
> with Errors 1 (see "Errors 1" below).
> There are quite few more errors. The checkdb ends with
> --CHECKDB found 0 allocation errors and 150 consistency errors in
> database 'DB_rpt1'.
> repair_allow_data_loss is the minimum repair level for the errors found by
> DBCC CHECKDB (DB_rpt1 ).
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.--
> ---
> At the time we saw absolutely no errors at ANY level (SAN, OS, etc) except
> when the SQL Server errorlog start screaming about --
> 2004-02-18 16:48:32.10 spid52 Error: 823, Severity: 24, State: 2
> 2004-02-18 16:48:32.10 spid52 I/O error (bad page ID) detected during
> read at offset 0x00000004a66000 in file
> 'w:\DBdata\DB_rpt1_data2.NDF'..--
> We had an HBA hardware failure 6 days later, we semi-attributed the
> corruption to the bad HBA.
> Could this be the 834628 problem? If so how can I tell - the KB is fairly
> non-specific about how to spot the error.
> Also would the fn_dblog function be of any use and what would I look for -
> the article seems to say that one line would be all zero's but this isn't
> that clear.
> ---
> Errors 1 --(this is the very beginning of the checkdb
> dump)--
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9523). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9524). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9525). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9526). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9527). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9528). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9529). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (4:9530). The PageId in the
> page header = (0:0).
> DBCC results for 'DB_rpt1'.
> CHECKDB found 0 allocation errors and 8 consistency errors not associated
> with any single object.
>|||My original theory still looks good - that the hardware was on the way out
and "glitched" writing bad data to disk. The article wasn't very clear on
cause and effect - so I had to ask.
Thank You !
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:u3mbNcOEEHA.1368@.TK2MSFTNGP11.phx.gbl...
> That is very unlikely a PAE problem. Errors like that are almost always
> attributable to bad blocks on disk. With an HBA on the blink, it is
likely
> that some bad data got written to the disk array, possibly where data was
> deleted since the pages are not owned by a specific object.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "frankm" <frank@.nxspxm.mallardcentral.com> wrote in message
> news:uHA$AJOEEHA.3472@.TK2MSFTNGP09.phx.gbl...
> was
> Server
starting
by
except
fairly
for -
isn't
the
the
the
the
the
the
the
the
associated
>|||Hi Frankm,
I agreed with Geoff N that it seems this problem is not mostly related the
problem in KB834628. Based on my experience, 823 errors are mostly hardware
related. Specially this error 823 on bad page ID is raised when the page ID
is invalid. When the error occurred, you can try to perform the following
steps to troubleshoot.
1. Check for error in the system and application from NT even viewer
2. Run DBCC checkdb on databse
a. IF it's sql 7.0, use "-y823" to start sql server and capture the dump
when the error is raised again
b. IF it's sql 2k, user DBCC Dumptrigger('SET', 823) to enable the dump
(this will NOT require the sql to be recycled!)
When the error 823 happens, it will catch the dump on it in sql errorlog,
3. Please also contact hardware vendor to run hardware diagnostic.
If the problem is very complex and you are unable to narrow down, you can
contact our PSS with the above information to continue working with a
dedicated Support Professional.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Thanks...
I have not used the DumpTrigger before - sounds really useful...
As I mentioned - there were absolutely NO errors at any other level - SAN,
OS, hardware -nothing.
The SAN people were in and could find no problem, keep in mind that the lun
was spread across 54 disks.
So the likelihood of it being a SAN problem was remote at best.
I had to ask the question -- Just in case it may be related...
Thanks for your help...
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PgR3kzUEEHA.616@.cpmsftngxa06.phx.gbl...
> Hi Frankm,
> I agreed with Geoff N that it seems this problem is not mostly related the
> problem in KB834628. Based on my experience, 823 errors are mostly
hardware
> related. Specially this error 823 on bad page ID is raised when the page
ID
> is invalid. When the error occurred, you can try to perform the following
> steps to troubleshoot.
> 1. Check for error in the system and application from NT even viewer
> 2. Run DBCC checkdb on databse
> a. IF it's sql 7.0, use "-y823" to start sql server and capture the dump
> when the error is raised again
> b. IF it's sql 2k, user DBCC Dumptrigger('SET', 823) to enable the dump
> (this will NOT require the sql to be recycled!)
> When the error 823 happens, it will catch the dump on it in sql errorlog,
> 3. Please also contact hardware vendor to run hardware diagnostic.
> If the problem is very complex and you are unable to narrow down, you can
> contact our PSS with the above information to continue working with a
> dedicated Support Professional.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>

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