 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Clustering / January 20052003 & SQL 2000 clustering Memory
Hello All Whats the recommendation for memory configuration on a single instance SQL2000 cluster running on Windows 2003. Each node has 8GB RAM. Do I still have to use the /PAE switch in Boot.ini to allow the OS to see 8GB or does 2003 see it all OK? Do I have to still enable AWE in SQL ? Can I still use the /3GB switch in the Boot.ini to restrict the OS to using 1GB RAM? - I remember seeing this done on a Windows 2000 Cluster. Do I still have to Cap the SQL memory if it is a single instance? Thanks in advance to any answers to all these questions. Fiona H. I have recently built 3 node cluster SQL 2000 & windows 2003, with a 8Gb of memeory I assigned 6GB to SQL server and 2 for the OS. Yes you need to use /PAE on windows 2003 to enable it to recoginze the 8Gb Mem Yes you will have to enable the AWE and configure the "Max Server Memory" to 6144 if you want 6Gb to be assigned to SQL. I dont think you need to use the /3GB. > Hello All > Whats the recommendation for memory configuration on a single instance [quoted text clipped - 8 lines] > Thanks in advance to any answers to all these questions. > Fiona H. I think that by default 2000 will allocate 2GB to OS and the other to Programs - is this still the case with 2003? I may try the /3GB switch anyway and allocate 7GB to SQL and do some tests. >I have recently built 3 node cluster SQL 2000 & windows 2003, with a 8Gb of > memeory I assigned 6GB to SQL server and 2 for the OS. [quoted text clipped - 19 lines] >> Thanks in advance to any answers to all these questions. >> Fiona H. Yes even in WIn2003 you need to set the /3GB to give the app 3 GB.  SignatureAndrew J. Kelly SQL MVP >I think that by default 2000 will allocate 2GB to OS and the other to >Programs - is this still the case with 2003? [quoted text clipped - 26 lines] >>> Thanks in advance to any answers to all these questions. >>> Fiona H. So I will be able to allocate 7GB to SQL then ? Fiona > Yes even in WIn2003 you need to set the /3GB to give the app 3 GB. > [quoted text clipped - 28 lines] >>>> Thanks in advance to any answers to all these questions. >>>> Fiona H. I see no reason why not. As long as you don't have other applications that require a good portion of memory that should be fine. SignatureAndrew J. Kelly SQL MVP > So I will be able to allocate 7GB to SQL then ? > Fiona [quoted text clipped - 30 lines] >>>>> Thanks in advance to any answers to all these questions. >>>>> Fiona H. I do not recommend using /3gb and /pae in boot.ini. If you are using both /3gb and /pae then do proper testing. Run Perfmon and monitor Free System PTEs under the Memory object to observe how many are free. Consider any value below 3000 as a minimum. NOTE: Low free page table entries can cause system instability. I would rather use just /pae in boot.ini and have awe enabled for sql and set max memory for sql = 6Gb. This would leave 2gb for OS and other programs/services. Ofcourse, in this case the assumption is that there is just one virtual SQL Server 2000 instance. Additional Information ================== Apply security update MS04-032 http://www.microsoft.com/technet/security/bulletin/ms04-032.mspx Best Regards, Uttam Parui Microsoft Corporation SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites: http://www.microsoft.com/protect http://www.microsoft.com/security/guidance/default.mspx What do you base that recommendation to not use the /3GB switch on? I have yet to see a system with only 8GB have a problem as long as you left at least 1GB for the OS and you were not running other apps on the server. SignatureAndrew J. Kelly SQL MVP >I do not recommend using /3gb and /pae in boot.ini. If you are using both >/3gb and /pae then do proper testing. Run Perfmon and monitor Free System [quoted text clipped - 34 lines] > http://www.microsoft.com/protect > http://www.microsoft.com/security/guidance/default.mspx I have seen some cases where there was unexpected failovers and/or node hangs. On troubleshooting, we found that they were using /3gb, /pae and awe enabled and Perfmon logs showed Free PTE very low. Removing the /3gb gave relief and did not reproduce the issue. In some cases we also used /userva (for win2K3). Thats the reason, I recommended testing the cluster nodes and making sure that Free PTE was not very low (i.e not less than 3000). Best Regards, Uttam Parui Microsoft Corporation SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites: http://www.microsoft.com/protect http://www.microsoft.com/security/guidance/default.mspx OK I have seen some similar cases but the low PTE's were usually cuased by applications on the server other than SQL Server or in most cases when there was more than 8GB of AWE. I agree this can be an issue under some extreme cases. I would emphasize the testing first a bit more strongly. SignatureAndrew J. Kelly SQL MVP >I have seen some cases where there was unexpected failovers and/or node >hangs. On troubleshooting, we found that they were using /3gb, /pae and awe [quoted text clipped - 24 lines] > http://www.microsoft.com/protect > http://www.microsoft.com/security/guidance/default.mspx Hello Andrew, The recommendations are based on the following KB article and also supporting customers with similar configurations that have faced OS stability issues: How to configure memory for more than 2 GB in SQL Server http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech Regards, Shashank Pawar SQL Server Support Engineer, Microsoft SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. -------------------- | From: "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> | References: <#aikJhBAFHA.824@TK2MSFTNGP11.phx.gbl> <991EF344-9DA1-4551-9BA8-78C9CE26FC4A@microsoft.com> <eGfTcbJAFHA.612@TK2MSFTNGP09.phx.gbl> <#laLrJMAFHA.3120@TK2MSFTNGP12.phx.gbl> <ey5dcnTAFHA.3592@TK2MSFTNGP09.phx.gbl> <uVcp0xVAFHA.3840@tk2msftngp13.phx.gbl> <5bn8LPdAFHA.3176@cpmsftngxa10.phx.gbl> | Subject: Re: 2003 & SQL 2000 clustering Memory | Date: Mon, 24 Jan 2005 08:50:50 -0500 [quoted text clipped - 8 lines] | NNTP-Posting-Host: h002078c8df25.ne.client2.attbi.com 24.61.176.109 | Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08 .phx.gbl!TK2MSFTNGP12.phx.gbl | Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.clustering:16385 | X-Tomcat-NG: microsoft.public.sqlserver.clustering [quoted text clipped - 41 lines] | > http://www.microsoft.com/protect | > http://www.microsoft.com/security/guidance/default.mspx That KB actually supports using the /3GB. Maybe even a bit too much in fact. Is there a KB that talks directly about these customer issues? If so that would be great to see. SignatureAndrew J. Kelly SQL MVP > Hello Andrew, > [quoted text clipped - 88 lines] > | > http://www.microsoft.com/protect > | > http://www.microsoft.com/security/guidance/default.mspx Many thanks for all your input folks > That KB actually supports using the /3GB. Maybe even a bit too much in > fact. Is there a KB that talks directly about these customer issues? If [quoted text clipped - 92 lines] >> | > http://www.microsoft.com/protect >> | > http://www.microsoft.com/security/guidance/default.mspx Many Thanks, i will take this one board >I do not recommend using /3gb and /pae in boot.ini. If you are using both >/3gb and /pae then do proper testing. Run Perfmon and monitor Free System [quoted text clipped - 34 lines] > http://www.microsoft.com/protect > http://www.microsoft.com/security/guidance/default.mspx |
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.