I have a SQL server 2000 server that completely stops responding at random parts of the day since around 3 weeks and I can only resolve the issue by rebooting. The server has been running good for about 3 months and now suddently this issue came by. What I mean by "stops responding" is that any queries from clients result on an ODBC timeout expired or a network general communication failure error. On the server itself, I can open enterprise manager but it freeze as soon as I try to expand the instance of the server. The server itself is still running good, I'm able to open other programs and able to remote control it without problems.
The processors are although running like they are having a hearth attack, running from 0 to 60% every second or so.
Memory usage is low (around the 300mb) and perfmon is not saying anything relevant on memory nor hard drives queue.
The error logs are not saying anything related to sql server or hardware problems (nor anything else actually).
Once the server gets rebooted, I see in the sql server logs that the logging completely stops when sql server freezes, it doesn't even log the server shut down. Also, if I try to get anything out of the perfmon on the sql server instance, any counter returns 1 static value, even on stuff that always move like lock requests per sec.
Nothing has changed before this behavior began on the server nor on the network.
We've changed the memory completely to rule out the possibility of a memory issue.
All diagnostics ran on the server returned nothing relevent.
I've changed the sql server memory allocation from dynamic to static and boosted the server's process priority, no changes.
The server is:
Sql server 2000 SP3 running on a Windows Server 2003 system, Xeon 2.6, 4 gig ram, raid 5 on data, mirror on os. OS, drivers, firmware and BIOS were updated last week (part of troubleshooting).
I really need help on this one, I've done a lot and need fresh ideas, its a production server!