February 2, 2009 at 7:49 am
At a glance, it appears you are starving the OS of much needed memory. If you have 3.8GB, I (personally) would allocate 2.8 for SQL server and leave 1Gb for the OS. And, I would move to sp4, although I don't believe that's what's causing your issue.
-- You can't be late until you show up.
February 2, 2009 at 7:58 am
Thanks for the reply...
Would 2.8Gb and 1Gb translate into modifying the SQL Server 2000 memory settings to 2.8Gb max and 1Gb min
February 3, 2009 at 9:10 am
Don't change anything for min server memory just change the max server memory to 2.8GB as other poster said.
MJ
February 3, 2009 at 9:36 am
MANU (2/3/2009)
Don't change anything for min server memory just change the max server memory to 2.8GB as other poster said.MJ
Agreed. Let SQL determine the lower limit, unless you're sure you want the minimum equal to ~x percent. But definitely change the max limit so that it doesn't starve other processes. What, besides SQL, is running on the server?
-- You can't be late until you show up.
February 4, 2009 at 3:58 am
It is a dedicated Server replicating data to another Cluster server.
The major application hogging the system is a .net sqlclient data provider @ 140k CPU
February 4, 2009 at 3:59 am
We have since updated to SP4 but with little effect on the excessive CPU
February 4, 2009 at 4:42 am
Is there any advantage in utilising the AWE switch and maximise on 2.8
Viewing 7 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply