Can AWE use >4GB RAM on SQL Server 2005 dev edition on Windows XP 32-bit -

Using the SQL Server 2005 Developer Edition on Windows XP Pro (32-bit) I noticed that the check box enables AW (Advanced). Winding extension) is enabled I have opteren workstation, which I can easily upgrade to 8 GB or more, although it is not practical to transfer 32-bit Windows XP to the development environment. As far as I can tell, for Opteron running in 32-bit mode, the Mmu should support 36-bit physical address space, which is equal to 32-bit Xeon.

Reducing the memory footprint of SQL Server will give me the Analysis Services and the Elbow Room.

• Does anyone know that the AWE supports more than 4 GB RAM on Windows XP, which can be used for SQL Server (with CPUs supporting AMU On)? Alternatively, does anyone know that the data docs view can tell me about the use of AWE buffer so that I can try it and certainly some views Can I obtain if he is using additional memory?

Edit: For those who are not familiar, AWE is a feature that lets you get virtual-physical address mapping and pages To make arbitrary physical process 4 GB in a virtual address space and out of memory. MMU at 32 bit Xeons (and some other processors) will actually support more than 4 GB of physical RAM, although the same process address space can only see 4 GB at a time. What can I say with the Mmu on Opteran, it also has this capability on 32-bit code.

SQL Server is backed up to use AVE to gain access to more than 2 GB or 3GB physical RAM, its process address space will allow 32-bit boxes to clear this mapping , Swap physical memory and outside the virtual address space. Some versions of Windows, especially Windows 2003 and Windows 2000 Advanced Services, will support more than 4 GB of memory in this way, and will provide an API to do this.

Question: Where I have a hardware support machine for it, should I use more than 4GB RAM in this way in Windows XP 32-bit?