February 24, 2006 at 1:15 pm
Guys
Which of the information is correct.
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
Based on the above link AWE is only available for Enterprise and Developer Edition.
Support for AWE is available only in the Enterprise and Developer editions and only applies to 32-bit operating systems.
But based on this artile.
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
It mention Standard Edition can take advantage of all the ram of
"Operating system"
Amit Lohia
February 27, 2006 at 8:00 am
This was removed by the editor as SPAM
March 2, 2006 at 6:36 pm
From what I've been able to understand from the literature, AWE was *necessary* to access certain amounts of memory in 32-bit versions. 64-bit versions allow access to that large amount of memory natively, and don't need AWE turned on. However, you still *can* turn on AWE on 64-bit systems (though you need some special security policy settings like "lock pages in memory"), and it does have effects. From what I understand, that AWE memory can't be used for query plans or other special cache stuff. However, the benefit is that it can prevent Windows from swapping out SQL Server's memory to disk. So if you have anything else happening on the 64-bit box, it might pay to have AWE to prevent Windows from stealing the physical memory from SQL (if you want to give SQL that kind of priority). Otherwise, it seems like AWE on 64-bit is a bad idea. That said, we're currently running AWE on a 64-bit dedicated SQL Server because we didn't realize that when we set it up. We plan to change it during the next maintenance window.
Some relevant links:
http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=83&threadid=45575&enterthread=y
http://blogs.msdn.com/slavao/archive/2005/11/15/493019.aspx
http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4451-8fdb-7134a004f94c/Adv64BitEnv.doc
http://searchsqlserver.techtarget.com/qna/0,289202,sid87_gci1161294,00.html?bucket=NEWS
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply