AWE on 2005 standard ed? | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

AWE on 2005 standard ed?

Quick question, as the specs on the web and in BOL seem ambiguous. Is it possible to run Windows Server 2003 Enterprise on a 32 bit system with SQL Server 2005 Standard using AWE to reach more than 4 gigs of RAM? Or is SQL Server 2005 Enterprise Edition required?
As far I know is 2005 EE required.
Luis Martin
Moderator
SQL-Server-Performance.com Although nature commences with reason and ends in experience it is necessary for us to do the opposite, that is to commence with experience and from this to proceed to investigate the reason.
Leonardo Da Vinci Nunca esperes el reconocimiento de tus hijos, eso ocurrirá luego de tu muerte
All postings are provided “AS IS” with no warranties for accuracy.
I think it is possible for SQL2k5 SE,http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx fyi. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
To be more specific: This http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx says, "Operating system maximum" – but it’s not clear if that means with or without AWE. I hope it means with AWE, and had assumed so. BUT BOL says, "Microsoft SQL Server 2005 Enterprise Edition uses the Microsoft Windows Address Windowing Extensions (AWE) API to support very large amounts of physical memory. SQL Server 2005 Enterprise Edition can access up to 64 gigabytes (GB) of memory on Microsoft Windows 2000 Server and Microsoft Windows Server 2003." and "SQL Server 2005 Enterprise Edition supports Address Windowing Extensions (AWE) allowing use of physical memory over 4 gigabytes (GB) on 32-bit versions of Microsoft Windows operating systems. Up to 64 GB of physical memory is supported. Instances of SQL Server running on Microsoft Windows 2000 use static AWE memory allocation, while instances running on Microsoft Windows Server 2003 use dynamic AWE memory allocation." and "Note:
Support for AWE is available only in the Enterprise and Developer editions and only applies to 32-bit operating systems." which statements have caused some doubt. I guess I’ll find out when we install it :-
The last note is true and I have had same response from MS Support when we are dealing other case at our end. AWE is not supported in SQL 2k5 SE. I’d just let SQL Server tune the memory until you see a specific reason to change it.
Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
That’s not very friendly of them. I don’t knock them for putting on that restriction (it’s their product, after all) but not explaining that clearly in the feature comparison is not nice. Not nice at all.
Well that is the downside of Microsoft *(always).. I agree that the notes are confusing to deliver correct information. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Some good news on this issue – file it under "proof in the puddin’?" <img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br /><br />We have built a test server and installed 2005 standard ed. The test server has 6 gig of RAM and the /PAE boot.ini switch (it’s a 32 bit system).<br /><br />I was able to turn on the SQL Server 2005 "Use AWE" memory setting, after granting the "Lock Pages in Memory" permission to the account under which it runs.<br /><br />Perf Mon &gt; SQL Server Buffer Manager &gt; Database pages shows 665,145 in use, vs. our SQL Server 2000 Standard Ed box, which shows only 185,000.<br /><br />If I have the math right, that means:<br /><br />2005 Standard Ed Data Cache: 665,145 pages / 128 pages per MB = 5,196 MB<br /><br /> 5,196 / 1024 = 5.07 GB <img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br /><br />2000 Standard Ed Data Cache: 185,000 pages / 128 pages per MB = 1,445 MB<br /><br /> 1,445 / 1024 = 1.4 GB<br /><br />So I think it works after all. Yay!<br /><br /><br /><br />
So with SQL 2005 on a 32 bit platform you must specify the /PAE switch in the boot.ini before SQL will be able to make use of the memory above 2GB??
BOL:
Support for AWE is available only in the Enterprise and Developer editions and only applies to 32-bit operating systems. SQL Server 2005 Analysis Services (SSAS) cannot take advantage of AWE mapped memory. If the available physical memory is less than the user mode virtual address space, AWE cannot be enabled. http://msdn2.microsoft.com/en-us/library/ms179301.aspx
Mohammed U.
quote:Originally posted by dtipton So with SQL 2005 on a 32 bit platform you must specify the /PAE switch in the boot.ini before SQL will be able to make use of the memory above 2GB??
Above 4Gb I believe.
Mark
Yes and in 64 bit you need not.
quote:Originally posted by dtipton So with SQL 2005 on a 32 bit platform you must specify the /PAE switch in the boot.ini before SQL will be able to make use of the memory above 2GB??

Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.
quote:Originally posted by MohammedU BOL:
Support for AWE is available only in the Enterprise and Developer editions and only applies to 32-bit operating systems. SQL Server 2005 Analysis Services (SSAS) cannot take advantage of AWE mapped memory. If the available physical memory is less than the user mode virtual address space, AWE cannot be enabled. http://msdn2.microsoft.com/en-us/library/ms179301.aspx
Mohammed U.

That was subsequently revised by MS — it was a documentation error. AWE DOES work in standard edition 2005 (we have a test server running in that configuration already, as I noted above)
]]>