awe settings.

SQL2K Ent SP3a Win2k SP3
I've recently enabled awe memory on 2 of our servers.
Everything seems to be going OK, AWE memory counters
are active in performance monitor and the sql serror log
shows awe memory enabled on startup.
My question is, is the above information enough to know that
awe is working correctly? If not, what other things can be looked
at?
TIA.see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274750#6
--
BR,
Mark Broadbent mcdba,mcse+i
_________________________
"Stressed" <k@.c.co.uk> wrote in message
news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
> SQL2K Ent SP3a Win2k SP3
> I've recently enabled awe memory on 2 of our servers.
> Everything seems to be going OK, AWE memory counters
> are active in performance monitor and the sql serror log
> shows awe memory enabled on startup.
> My question is, is the above information enough to know that
> awe is working correctly? If not, what other things can be looked
> at?
> TIA.
>
>|||Also, when SQL Server starts you should see a line time in
the event log that says:
"Address Windowing Extensions enabled."
Ron
>--Original Message--
>see
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q274750#6
>--
>BR,
>Mark Broadbent mcdba,mcse+i
>_________________________
>"Stressed" <k@.c.co.uk> wrote in message
>news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
>> SQL2K Ent SP3a Win2k SP3
>> I've recently enabled awe memory on 2 of our servers.
>> Everything seems to be going OK, AWE memory counters
>> are active in performance monitor and the sql serror log
>> shows awe memory enabled on startup.
>> My question is, is the above information enough to know
that
>> awe is working correctly? If not, what other things can
be looked
>> at?
>> TIA.
>>
>>
>
>.
>

AWE memory performance counters

Where can I get a definition of what the Performance Monitor counter
relating to AWE memory mean? Also, what are normal ranges for these
counters, what would be considered "high"
The counters I'm referring to are:
SQLServer:Buffer Manager\AWE lookup maps/sec
SQLServer:Buffer Manager\AWE stolen maps/sec
SQLServer:Buffer Manager\AWE stolen maps/sec
SQLServer:Buffer Manager\AWE unmap calls/sec
SQLServer:Buffer Manager\AWE unmap pages/sec
SQLServer:Buffer Manager\AWE write maps/sec
Any input is appreciated.The definition can be found at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_0ugk.asp.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Ed Thibert" <ethibert@.dlbabson.com> wrote in message
news:OdUd0D4rDHA.732@.TK2MSFTNGP09.phx.gbl...
> Where can I get a definition of what the Performance Monitor counter
> relating to AWE memory mean? Also, what are normal ranges for these
> counters, what would be considered "high"
> The counters I'm referring to are:
> SQLServer:Buffer Manager\AWE lookup maps/sec
> SQLServer:Buffer Manager\AWE stolen maps/sec
> SQLServer:Buffer Manager\AWE stolen maps/sec
> SQLServer:Buffer Manager\AWE unmap calls/sec
> SQLServer:Buffer Manager\AWE unmap pages/sec
> SQLServer:Buffer Manager\AWE write maps/sec
>
> Any input is appreciated.
>

AWE and Perfmon Counters

We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now having
problems seeing true memory utilization by SQL Server. For example, Task
Manager shows SQL only using 174,712 k when it has been configured to 13gb.
Not to mention perfmon memory object is not reporting accurately either.
With that said, is this a known issue and what is the work around? I want
to be able to guage if we need more than 16gb on this box.
Thanks!
MichaelTask manager cannot count higher than 2GB of memory. The performance
monitor counters will give accurate memory usage. Another quick and dirty
way is to look at Page File usage. AWE usage shows up as page file
committment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:48B6C39B-8DB3-4B20-B487-935ADF37D952@.microsoft.com...
> We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now
> having
> problems seeing true memory utilization by SQL Server. For example, Task
> Manager shows SQL only using 174,712 k when it has been configured to
> 13gb.
> Not to mention perfmon memory object is not reporting accurately either.
> With that said, is this a known issue and what is the work around? I want
> to be able to guage if we need more than 16gb on this box.
> Thanks!
> Michael
>

AWE and Perfmon Counters

We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now having
problems seeing true memory utilization by SQL Server. For example, Task
Manager shows SQL only using 174,712 k when it has been configured to 13gb.
Not to mention perfmon memory object is not reporting accurately either.
With that said, is this a known issue and what is the work around? I want
to be able to guage if we need more than 16gb on this box.
Thanks!
Michael
Task manager cannot count higher than 2GB of memory. The performance
monitor counters will give accurate memory usage. Another quick and dirty
way is to look at Page File usage. AWE usage shows up as page file
committment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:48B6C39B-8DB3-4B20-B487-935ADF37D952@.microsoft.com...
> We have enabled AWE on our SQL 2000/Win 2003 Ent servers and are now
> having
> problems seeing true memory utilization by SQL Server. For example, Task
> Manager shows SQL only using 174,712 k when it has been configured to
> 13gb.
> Not to mention perfmon memory object is not reporting accurately either.
> With that said, is this a known issue and what is the work around? I want
> to be able to guage if we need more than 16gb on this box.
> Thanks!
> Michael
>