May 23, 2008 at 3:13 am
I’m having a few issues with a server that keeps grinding to a halt and having frequent system issues requiring a reboor. It is Sql 2000 32 bit enterprise edition running 64 bit 2003 server. Im not sure of the impact of having the AWE switch set for this server because even though it has 8Gb of RAM it is only using 262Mb and is used extensively. It is set to dynamically configure sql server memory with a minuimum memory of 3075 and maximum of 6144
Is it worth me removing the AWE option or are there any more tweaks I can make to make this system run more effectively?
May 24, 2008 at 2:40 am
Doesn't AWE require fixed memory instead of dynamic allocating?
Up to date with servicepacks (sp4 has an AWE bug fixed by a hotfix)
May 28, 2008 at 4:39 am
I think you will probably find that because you have not specified a mem amount to be locked by AWE that is why it have locked 256MB (minimum requirement).
I have never actually used AWE myself (always told to stay well cllear). However if you must use it, you do need to specify the amount of memory to lock. You might need to use it in conjunction with AWE or PAE in your OS as well (gets very merky).
This article talks about AWE only using 256MB (hope its of some help): http://msdn.microsoft.com/en-us/library/ms190673.aspx
Adam Zacks-------------------------------------------Be Nice, Or Leave
May 28, 2008 at 8:56 am
I must admit I'm running SQL2K3, 32 bit but I think this will apply. Awe needs to be enabled, /PAE should be in your boot.ini file and the account running SQL server also needs the rights to lock pages in memory. Fixed memory is preferred/recommended. I leave about 1-1.5 GB for the OS for a dedicated SQL server.
-- You can't be late until you show up.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply