AWE got 0, said DBCC MEMORYSTATUS...

I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc
.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
-- restart the sql
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'min server memory', 1024
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
The box is a:
Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
That's a WinServer 2003 64-bit.
Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
bpool_commit_target bpool_visible
-- -- --
-- --
8584736768 2147352576 5280 199912
199912
Am I doing it right? How to verify my stuff are consuming memory from the
AWE?
Thanks.You can use Performance on Windows and verify Memory Manager, Total Server
Memory.
Check your SQL Server log when the instance was started, there must be a
'Address Windowing Extensions enabled' message. If AWE was not succesfully
started there must be a related error message.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"light_wt" wrote:

>
> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, e
tc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||Did you add your SQL Server service account to "Lock pages in memory" list
before performing this action?
Otherwise, it would not let you set AWE enable.
How to: Enable the Lock Pages in Memory Option (Windows):
http://msdn2.microsoft.com/en-us/library/ms190730.aspx
Ekrem ?nsoy
"light_wt" <lightwt@.discussions.microsoft.com> wrote in message
news:2217E528-6E89-4C83-987C-FAA270A30FE3@.microsoft.com...
>
> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0,
> etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||Also, there are AWE specific counters under SQLServer:Buffer Manager. Take a
look at these AWE counters to see if there are any AWE-related memory
activities.
Linchi
"light_wt" wrote:

>
> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, e
tc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||thanks everyone for your ideas.
i've look at the SQL Server Log, after the instances started, the AWE is
enable.
i've check the userid who can do Lock Memory and is the same perosn who own
the Job.
in perfmon, I have added all AWE-related counters in SQLServer:Buffer
Manager
and changed the vertical counter to 5.
nothing happen. AWE got 0.
Am I missing something?
thanks.