 |
 | 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 / July 2008Memory allocation question
Hello, I'm running a 4 node active SQL 2000 cluster. Each server is running Windows 20003 Enterprise with 16gb of RAM (server sees all of the memory). Each server has the "Dynamically configure SQL server memory" option enabled. I'm not all that familiar with SQL and I assumed that by configuring the servers this way that SQL would be able to use most of the physical RAM in the server when needed but now I finidng articles that mention the /3gb /AWE switches. So what is the story? Do I need to enable these switches? If SQL 2000 does have a memory limit why does it then show a maximum memory limit of 16gb? This just doesn't make sense and is very misleading. If someone can point me the right direction it would be greatly appreciated. thx. -AJ- > Hello, > [quoted text clipped - 19 lines] > > -AJ- For Windows 2000 that was a requirement in order to allow SQL Server Ent Ed (and datacenter) to access more than the 4GB of RAM in the server. For Windows 2003 these options are set dynamically by the system itself. On the SQL Server 2000 side of things, it sounds like someone has already enabled the advanced option of 'awe enabled'. Normally, you would have to run the following commands to allow SQL 2k to access the extra AWE RAM. exec sp_configure 'show advanced options', 1 RECONFIGURE GO exec sp_configure 'awe enabled', 1 RECONFIGURE GO Then restart the MSSQLServer service. Rick Sawtell You failed to mention the single most important piece of information here: are the servers (and OS and SQL code) 32 bit or 64 bit??  SignatureKevin G. Boles Indicium Resources, Inc. SQL Server MVP kgboles a earthlink dt net > Hello, > [quoted text clipped - 19 lines] > > -AJ- Rick, How can I tell if the AWE option is already enabled? SQL Guru, 32bit. thx. > You failed to mention the single most important piece of information here: > are the servers (and OS and SQL code) 32 bit or 64 bit?? [quoted text clipped - 22 lines] > > > > -AJ- Run the following code in Query Analyzer and see if the Running Value is 1 exec sp_configure 'awe enabled' If it yields "The configuration option 'awe enabled' does not exist, or it may be an advanced option." then run the following code exec sp_configure 'show advanced options', 1 RECONFIGURE GO now try the following again to see if AWE is enabled or not. exec sp_configure 'awe enabled' You should enable this feature to let your SQL Server take advantage of this 16GB RAM. You better don't use /3GB. So you'll let the OS use 2GB of RAM for itself. Ensure you have /PAE in your boot.ini file (under the root of the OS) See the following KB: http://support.microsoft.com/kb/283037/en-us SignatureEkrem Önsoy > Rick, > [quoted text clipped - 37 lines] >> > >> > -AJ- Yeah, for 16GB of RAM, I would >not< set /3GB in the boot.ini file. Linchi > Run the following code in Query Analyzer and see if the Running Value is 1 > [quoted text clipped - 61 lines] > >> > > >> > -AJ- Gotta say it is kinda scary that you seem to be responsible for a pretty significant SQL Server installation but didn't know what is pretty basic stuff for configuring sql server on such hardware. Makes me think there are likely a bunch of other things that are suboptimal. Find yourself a good consultant for a performance review and learn from them how to monitor and tune the servers. This could be a BUNCH of issues you won't even know to ask about using the forum for support and advice. For a 32 bit sql server box with 16GB ram you need AWE enabled, /PAE in boot.ini. You CAN set /3GB but there are factors that need to be evaluated to determine if that is appropriate. Max mem needs to be set, etc, etc. SignatureKevin G. Boles Indicium Resources, Inc. SQL Server MVP kgboles a earthlink dt net > Rick, > [quoted text clipped - 37 lines] >> > >> > -AJ- >Gotta say it is kinda scary that you seem to be responsible for a pretty >significant SQL Server installation but didn't know what is pretty basic >stuff for configuring sql server on such hardware. Makes me think there are >likely a bunch of other things that are suboptimal. Hey at least he's trying, so many places have nobody in charge, do I have stories! J. Personally I am quite happy there are LOTS of places like that. I get the lion's share of my business from companies like that who come to the stark realization that they have dug themselves into a hole so deep that regardless of whatever hardware they can afford to throw at it the system is still non-performant!! :-)) SignatureKevin G. Boles Indicium Resources, Inc. SQL Server MVP kgboles a earthlink dt net >>Gotta say it is kinda scary that you seem to be responsible for a pretty >>significant SQL Server installation but didn't know what is pretty basic [quoted text clipped - 6 lines] > > J. |
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.