October 3, 2006 at 10:42 am
Just installed 2k5 on a 32-bit Server 2003 Ent. system with 8gb of ram. Have the /3gb and /pae switches in boot.ini. AWE is enabled in SQL Server properties.
Server Properties/General reports 8191 (MB) for memory, which is correct. However, a check of the SQL Agent log reveals this message: "[310] 4 processor(s) and 4096 MB RAM detected"
Why the discrepancy? Are my settings working? Will SQL Server use the 8gb when we start pushing this system?
October 3, 2006 at 11:05 am
Forgot to mention, I'm using the eval edition until we receive the enterprise media.
October 4, 2006 at 2:45 am
SQL Agent is not AWE-aware, so it cannot use any memory above the 4GB line. The memory value it reports will depend on the API call it made to Windows. Just a guess, but it may reporting only how much memory is available to SQL Agent, not how much is actually on the box.
You will also find that the memory usage reported in Windows Task Manager does not include any AWE memory use. This is because Microsoft only wrote Task Manager to look at directly addressable memory.
I just checked one of our boxes that has 6 GB memory, and the AWE memory counters show SQL is using the extra memory, but Agent is reporting only 2GB available at startup.
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
October 4, 2006 at 7:56 am
Thanks for the info, Ed. I didn't know that SQL Agent isn't AWE-aware.
October 4, 2006 at 8:25 am
The only functionality in the whole of the SQL2000 and SQL2005 32-bit product set that is AWE-aware is the database buffer pool. All other storage in the 32-bit versions of both of these products has to live below the 4GB line.
In 64-bit SQL2000 there are still a lot of components that have to live below the 4GB line, as MS only ported limited functionality to 64-bit.
In 64-bit SQL2005 all components can use the full 64-bit address space.
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