AWE on 64-bit machine
-
Hi,
We just got a 64-bit machine with 2 AMD Opteron processors. It has 32 GB RAM. We installed 32-bit SQL Server 2000 on it.
Now my question is should we enable AWE on this machine to access the maximum of available 32 GB RAM?
Regards,
RSingh
-
So, you had a steam locomotive and have just purchased a diesel and want to know where to put the coal in so it works?
AWE is not relevant with 64-bit. You have access to the full 32GB memory simply because you are now running 64-bit.
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
-
If you are running 32-bit SQL Server with a 32-bit Windows operating system, the 64-bit capability of the hardware isn't doing you any good and you need to enable AWE to use memory above 4GB. You would be much happier with the performance if you used 64-bit versions of Windows and SQL Server.
-
Do I need to enable AWE if I am running 32-bit SQL Server with a 64-bit windows operating system (Windows Server 2003 R2 x64)?
-
No, you need to install 64-bit SQL Server
-
I guess my question was if we still running 32-bit SQL server with 64-bit Windows do we need to enable AWE?For some reason, we have to run 32-bit SQL server now.
-
YES.
Since you are using 32-bit SQL Server you still need to enable AWE. You can do away with enabling AWE only if you are using 64-bit SQL Server.
On Windows Server 2003 Enterprise Edition R2 x64 you can access up to 32 GB of RAM.
-
My answer was meant to be a jest, maybe I didn't use enough smileys. Yes, you need to enable AWE in any 32-bit edition of SQL Server to use memory over 4GB, regardless of whether the OS is 64-bit. I wasn't sure if SQL 2000 32-bit on Windows 2003 x64 is a valid configuration, it isn't shown on the MSDN web page for "Operating Systems Supported by the Editions of SQL Server 2000". I have no experience with 32-bit SQL on a 64-bit OS, I would do some research on any problems with AWE in this configuration before I went ahead with it.
You will be much happier if you can identify who or what is keeping you from installing 64-bit SQL (preferably SQL 2005), and remove the impediments. I realize there are many reasons to be stuck with legacy compatibility issues, hopefully you can resolve yours.
32-bit SQL with AWE can use the extra memory, but only for the page buffer. Other memory structures used for the procedure cache, connections, locks, sorting & hashing, etc. do not benefit. The 64-bit edition can use memory much more efficiently.
This is a Microsoft video that includes a 32-bit vs 64-bit comparison on otherwise identical hardware. The 64-bit server handles 5 times the load of the 32-bit server. Advance the timer to 36:00 to go straight to the SQL demo. http://www.microsoft.com/winme/0505/24527/winhec_20050425_300.asx
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply