August 4, 2009 at 2:46 pm
I was reading somewhere that I should enable lock pages memory , reboot and then enable the AWE.
I may not have followed this exact order.
Should I try that?
August 4, 2009 at 10:34 pm
Rebooted the machine twice and it worked this time:)
Thanks for all the help
August 6, 2009 at 9:59 am
There are some things to consider..
1) Task Manager on a 32-bit server cannot show memory use above the 4GB line. Even if your SQL instance has 20GB AWE memory allocated the Task Manager will show a maximum of about 1.6 GB memory used.
2) To see details of what AWE memory is used, ther are 2 places to look: a) In the SQL Error log at startup. You should see a message about how much AWE memory has been allocated, or a message saying AWE was not used. b) The AWE performance counters will show you the level of activity of AWE pages, but not the total amount of memory in use.
3) SQL Server 32-bit can only use the memory above the 4GB line as a data cache. For all other processing it has to use memory below the 4GB line. On a 32 GB server you are unlikely to ever see SQL Server using more than 1.6 GB.
4) If you want the best performance, run SQL Server on a 64-bit box.
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
August 7, 2009 at 5:05 am
With AWE in use on x86:
Performance Monitor Counters:
SQL Server: Buffer Manager: Total pages (multiply by 8KB) = data cache size
Process: sqlsrvr: PrivateBytes = other memory allocations, including mutli-page allocations ("MemToLeave")
So adding these together gives the total memory committed by SQL Server.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply