June 15, 2006 at 10:56 am
Dear friends,
I have a SQL 2000 server enterprise edition on a windows 2003 enterpise edition server having 16 GB ram.I have enabled PAE but not AWE.Still in the enterprise manager properties Memory tab I find that I can allocate upto 16 GB dynamically.
However in the SQL server :memory manager performance monitor I can only see upto 1.6 GB in the Total and Target server memory allocated..
Is the enterprise manager memory setting not showing the correct picture in this case?
Thank you,
kg
KG
June 15, 2006 at 11:06 am
Perfmon and Task Scheduler do not properly show the memory utilization when AWE is enabled. You can use DBCC MEMORYSTATUS as per these Microsoft KB article (the SQL Server 2005 has a note in the introduction that states Perfmon and Task Scheduler has issues):
INF: Using DBCC MEMORYSTATUS to Monitor SQL Server Memory Usage
How to use the DBCC MEMORYSTATUS command to monitor memory usage on SQL Server 2005
K. Brian Kelley
@kbriankelley
June 15, 2006 at 11:24 am
Thanks kelley.
But I haven't enabled AWE uptill now!.But still the enterprise manager memory tab is allowing me to allocate all 16 GB. Thats my primary confusion.
Thanks ,
kg
KG
June 15, 2006 at 11:29 am
I believe that it will allow you to allocate the maximum, but without the /PAE switch, the maximum SQL Server will actually use is 2 GB (3GB if /3GB is used in boot.ini).
K. Brian Kelley
@kbriankelley
June 16, 2006 at 4:23 am
If you have not turned on AWE, then regardless of the amount of memory you allocate to SQL Server, it will not use anything above the 4GB line.
If you have the /3GB switch in BOOT.INI, then SQL will use 3GB, otherwise it will use a maximum of 2GB when AWE is not enabled.
When you enable AWE, SQL can use memory above the 4GB line for database bufferpool storage. All other memory use apart from the database bufferpool remains below the 4GB line.
Windows task manager does not correctly report usage of any memory above the 4GB line. However, when you turn on AWE, you get a new set of SQL performance counters that track your AWE usage.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply