We are currently testing an application that accesses SQL Server. We tend to monitor the processor usage quite a lot.
Every so often the everything seizes up. We can shut down the application we are testing, but SQL Server still seems to be using 99% of the processor.
Even when we stop the services SQL Server doesn't let go of the processor. the only thing we can do is reboot the server when this happens (hardly the most practical solution).
Any bright ideas? Why would this happen and what can we do about it?
Every so often the everything seizes up. We can shut down the application we are testing, but SQL Server still seems to be using 99% of the processor.
Even when we stop the services SQL Server doesn't let go of the processor. the only thing we can do is reboot the server when this happens (hardly the most practical solution).
Any bright ideas? Why would this happen and what can we do about it?