InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 08:01:21 GMT20http://www.sqlservercentral.com/Forums/Topic540972-146-1.aspx[quote][b]jim.powers (7/28/2008)[/b][hr]If that switch is not already there, it does need to be added.[/quote]on the very rare odd occasion and normally for older processor architecture. 99% of the time the processor architecture will automatically configure the boot.ini at install time with the DEP option /noexecute. This switch implies and automatically switches on /PAEMon, 28 Jul 2008 12:53:40 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic540972-146-1.aspx[quote][b]Perry Whittle (7/28/2008)[/b][hr][quote][b]Milton Gonsalves (7/25/2008)[/b][hr]So only Enabling /PAE should also help.., right?[/quote]if your using win 2003 enterprise it should address all the RAM straight off without editing the boot.ini[/quote]When installing Win 2003 Enterprise (32-bit), it will automatically recognize the need for the /PAE switch and should add it automatically to the boot.ini. If that switch is not already there, it does need to be added. Win 2003 64-bit does not require the /PAE switch, 32-bit does.Mon, 28 Jul 2008 11:16:38 GMTjim.powershttp://www.sqlservercentral.com/Forums/Topic540972-146-1.aspx[quote][b]Milton Gonsalves (7/25/2008)[/b][hr]So only Enabling /PAE should also help.., right?[/quote]if your using win 2003 enterprise it should address all the RAM straight off without editing the boot.iniMon, 28 Jul 2008 06:30:01 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic540972-146-1.aspx[quote][b]Milton Gonsalves (7/25/2008)[/b][hr]So only Enabling /PAE should also help.., right?[/quote]Not from what I have read. PAE just lets windows utilize all the memory. AWE has to be turned on in SQL for SQL to be able to use more.Edit: We didn't see the performance increase until we turned on AWE in SQL.Fri, 25 Jul 2008 11:20:30 GMTjason.stephenshttp://www.sqlservercentral.com/Forums/Topic540972-146-1.aspxSo only Enabling /PAE should also help.., right?Fri, 25 Jul 2008 11:00:28 GMTsqldba20http://www.sqlservercentral.com/Forums/Topic540972-146-1.aspxensure you configure the "lock pages in memory" local security policy for the account SQL runs under. Generally its not recommended to use the /3GB switch for machines with 16GB RAM and over. Using the /3GB switch with machines using large amounts of RAM (reportedly 12GB and over) can effect the way the machine addresses the memoryFri, 25 Jul 2008 10:01:08 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic540972-146-1.aspxThat is what we did but we capped ours at 12 GB. It showed incredible gains in efficiency.Edit: ours was only SQL 2000 that we did this on.Fri, 25 Jul 2008 09:15:11 GMTjason.stephenshttp://www.sqlservercentral.com/Forums/Topic540972-146-1.aspxAll:We have a new Windows server and are working on configuring the memory. Read a lot about /3GB , /PAE , AWE and got a little bit confused so thought I will post it here and see what do you folks thinks how I am going to configure?Our New Windows Environment.Windows 2003 Enterprise Edition (32 bit)Memory - 16 GBSQL 2005 Enterprise Edition (32 bit)I would like to give not more than 2 GB for the OS / Kernel (14 GB we want for SQL) and based on that here is what I am planning to configure. Let me know if I am right or wrong?On Windows Enable the /3GB /PAE switchOn SQL Server Enable AWE and set the MAx Server Memory to 14 GBThanks !Fri, 25 Jul 2008 08:41:40 GMTsqldba20