March 13, 2007 at 10:43 am
I just installed a SQL server 2005 64 bit, Ent on windows 64 bit. The max memory to be used was set to 2GB by default. And I have a check box available to employee the AWE.
Do I need to set in the boot file PAE, AWE in 64 bit (the way we do on 32bit)so the SQL server could use more then 2 GB of memory? I have 8 on the server and wanted to give at least 5.5 to the SQL server
Thanks a lot, mj
March 13, 2007 at 12:19 pm
Because of the 64bit archictecture you no longer need to use the PAE switch in the boot.ini file. You do not need the AWE or the /3GB any longer to fool the OS. You should be able to set the max mem to 5.5GB or I would vote for 6GB. The change should be dynamic. It should not require a restart or reboot.
March 14, 2007 at 4:43 am
I have seen the AWE checkbox on 64-bit SQL, but have not found out yet if it is ignored or harmful. There is no way that selecting AWE on 64-bit SQL can be helpful, so I would suggest you leave it clear.
You may see 'Physical Address Extensions' shown on the My Computer properties screen on a 64-bit server. In this case Windows is merely reporting the hardware properties of the chipset, not necessarily that /PAE has been added to boot.ini. Both /PAE and /3GB are not needed on a 64-bit box.
You can set SQL memory at any time, up to the maximum available on the server. However, as with 32-bit SQL, you need to allow enough unused memory to keep Windows happy and for any other tasks that get run often (such as backups). You need to look at your own environment to decide if SQL can take 5.5 GB or 6 GB. Leaving less than 2 GB for Windows, etc, could put pressure on memory giving extra paging and harming performance.
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
March 15, 2007 at 4:35 am
on 64 bit, I would recommend you to give "lock pages in memory" right to your SQL Server service account. (Local Security Policy -> Local Policy -> User Rights Assignment -> explicitly add your user to lock pages in memory right . and reboot OS)
Also, leave around 1-2 GB for your OS. so if you have 8 GB of RAM, you may want to set max server memory for SQL to 6-7 GB of RAM.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply