 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / DB Engine / SQL Server / March 2008BOOT.INI File for 4GB RAM and SQL 2005
I have 3 questions regarding memory configuration on a Windows Server 2003 SP2 Enterprise Edition with SQL2005 SP2. 1. Can someone advise on the correct boot.ini file configuration to utilize 4GB of local memory? I'm not sure if I need the 3GB switch? multi(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise"/3GB/fastdetect/PAE/NoExectute=OptOut 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is the sp_configure awe enabled config_value=1 and run_value=1 ? 3. Assuming nothing else is to be done to have SQL 2005 utilize more than the 2GB memory space, how do you verify or validate SQL 2005 is using more memory? Thanks in advance zorro Is it 64 bit or 32 bit? > 1. Can someone advise on the correct boot.ini file configuration to > utilize > 4GB of local memory? I'm not sure if I need the 3GB switch? You do need 3GB switch > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is > the sp_configure awe enabled config_value=1 and run_value=1 ? AWE is for utilyze more than 4GB Yes, unless you use 64 bit , then you do not need AWE , make sure that an account SQL Serverc runs under is added to LockPages in Memory Local Group Policy > 3. Assuming nothing else is to be done to have SQL 2005 utilize more than > the 2GB memory space, how do you verify or validate SQL 2005 is using more > memory? Task Manager >I have 3 questions regarding memory configuration on a Windows Server 2003 > SP2 Enterprise Edition with SQL2005 SP2. [quoted text clipped - 14 lines] > > Thanks in advance >> 3. Assuming nothing else is to be done to have SQL 2005 utilize more than >> the 2GB memory space, how do you verify or validate SQL 2005 is using >> more >> memory? > > Task Manager Actually, I would use performance monitor. Task manager tends to under-report what SQL Server is actually using. Aaron I agreee. I assumed the OP wants to utilize 4GB ONLY , so after adding 3GB switch you can actually observe in TM. >>> 3. Assuming nothing else is to be done to have SQL 2005 utilize more >>> than [quoted text clipped - 6 lines] > Actually, I would use performance monitor. Task manager tends to > under-report what SQL Server is actually using. Thanks Uri, 1. 32 bit Windows Server 2003 version. 2. To verify 3GB switch is needed for my 5GB physically installed RAM? 3. Also good catch on the LockPages in Memory setting within the gpedit.msc Thanks, zorro > zorro > Is it 64 bit or 32 bit? [quoted text clipped - 36 lines] > > > > Thanks in advance See comments inline. Linchi > zorro > Is it 64 bit or 32 bit? [quoted text clipped - 3 lines] > > You do need 3GB switch Why? > > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is > > the sp_configure awe enabled config_value=1 and run_value=1 ? > > AWE is for utilyze more than 4GB I keep hearing that AWE is for utilizing more than 4GB. Not sure where that comes from. Technically, it's not. > Yes, unless you use 64 bit , then you do not need AWE , make sure that an > account SQL Serverc runs under is added to LockPages in Memory Local Group [quoted text clipped - 24 lines] > > > > Thanks in advance Hi Linchi You are right, that technically, it's not. If I have 4GB RAM and want tio utilize 3GB for SQL Server, so I simple add switch in BOOT.INI and why bother enabling AWE? What do you think? > See comments inline. > [quoted text clipped - 56 lines] >> > >> > Thanks in advance |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.