Hello- This would be a first time post for me. I am a sys admin with little SQL experience, so I am learning as I go here. We have a server running dual 1.4 GHZ processors with a Gig of RAM with RAID 5 configuration. The server runs only SQL server 2000 as well as IIS because this server is dedicated to run an application using IIS that works in conjunction with some SQL databases on the same server. Also there are users (about 15-30 at one time max) that use an Access FE that the customer programmed that interacts with some other SQL databases on the BE on the same server. Also running on the server is .NET Framework 1.1 which is needed to interact with the application software. Now saying that, here is the problem: Every other day I am having to reboot the server because the CPU resources appear to be 100% utilized. Symptoms: It takes awhile to log onto the machine, it takes awhile to run any application period, programs stop responding after you try and open them, The access FE connection to the SQL on the customer side runs extremely slow, The web application's connections to the SQL databases run extremely slow, Tivoli monitoring stops responding, etc. Once I reboot the machine, it is fine for about a day and then this happens all over again. The real enigma is that in task manager, the CPU utilization averages 10% usage, the memory usage shows about 250 MB free, and none of the processes except sqlsrvr.exe show any real memory usage. I have read around on the net and they say SQL server is designed to use up most available memory and will not release it back to the server unless it is requested. I read the Performance Monitoring section of this website and tracked the performance of: Process Object: % Processor Time System Object: Processor Queue Length. System: Context Switches/Sec Processor time averaged 199. something, processor queue length averaged about .3, and context switching maxed at 1600. I have talked to the vendor of the software running on the machine because it appears that since the upgrade to their latest software we have had this problem more frequently. They are claiming there are no known issues, so I am wondering if there is something in SQL that could be causing these problems? In the past I have monitored the servers because the same thing happened even before the upgrade, but just not as often. I am left scratching my head and have no clue what could be causing this. It appears something is using the CPU resources, but none of the performance monitors are picking it up. If anyone could help out I would greatly appreciate it. Thanks!