Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
icw
Constraint Violating Yak Guru
378 Posts |
 Posted - 2007-07-24 : 07:30:09
|
| Hi I have a Windows 2003 Server Enterprise edition with 16GB of RAM and 16 Processors.Currently I have just installed SQL Server 2000 Standard edition. (I understand that this version only support 4 cpus and 4GB RAM....Can anyone concur with this?)Interestingly when I go into the EM and select "Use all processors" it does seem to show all 16. Does this mean that it will use all 16 or that despite showing all 16 only four will be used.Thanks for any help |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-24 : 14:52:21
|
| You can double check in perfmon. By the way, standard edition can only use 2gb memory. |
 |
|
|
icw
Constraint Violating Yak Guru
378 Posts |
Posted - 2007-07-26 : 04:47:59
|
| Thanks for your reply,I have now put them on SQL Server 2000 Enterprise Edition. To make use of all CPU's and available RAM.HOWEVER - someone has just told me that we might need to enable something called AWE Memory support (We are using Windows 2003 Enterprise Server and SQL Enterprise as well - so is this person right or wrong?)CheersICW |
|
|
|
icw
Constraint Violating Yak Guru
378 Posts |
Posted - 2007-07-26 : 06:58:39
|
| I've been doing some reading, it definitely looks like I will need to enable AWE. Can anyone tell me the best way to do this. And/or give any pitfalls to look out for? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-26 : 23:17:02
|
| If it's dedicated sql server, I'll add '/3gb' and '/pae' in boot.ini file, enable awe with sp_configure, set max memory in sql to 15gb, and apply sql2k sp4a. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-07-26 : 23:45:54
|
| /3gb switch and /pae switch alone with 16GB RAM is a bad idea. You will most likely run out of system PTEs and the SQL Server will go sideways.My recommendation is to use the /userva setting as well. This allows you to tune the per process memory allocation to somewhere between 2GB and 3GB giving you more system PTEs and eliminating this particular problem. here is the KB article on this http://support.microsoft.com/kb/316739/en-usI don't really recommend using /3gb and /pae by themselves on a SQL system with 12GB or more of RAM. Keep in mind, this only applies to the 32bit OS and SQL2K. 64bit stuff does not have any of these issues.Do some searching in the microsoft knowledgebase for /3gb, /pae and /userva to get some more understanding of what it is you are changing.-ec |
|
|
|
|
|
|
Memory and processor support