CPU Usage pegged at 100%

Last night we had reports that our website was not responding. After some
investigation we found that the issue was SQL Server had all of the CPU's
pegged at 100% on a server that usually runs no higher than 10%. Our site
was not exceptionally busy, nor have we installed anything new that accesses
the database recently. In the sQL Server Error Log I see alot of "buffer
latch errors", but they appear to have occurred after CPU usage had already
hit 100%.
No one here is really a SQL Server troubleshooting or tuning expert. What
should we do to try to determine the cause?
Thank you
Evan,
This can be difficult to track down because you really do not have any idea
what was occuring at the time. You might consider creating an automated
proactive solution to tracking these kinds of issues by using Profiler,
jobs, alerts (performance condition alerts included), SysMon, MOM 2005
and/or a related third-party product.
HTH
Jerry
"Evan Nelson" <EvanNelson@.discussions.microsoft.com> wrote in message
news:CB0D7602-453D-4D35-A09C-9672D7B47E29@.microsoft.com...
> Last night we had reports that our website was not responding. After some
> investigation we found that the issue was SQL Server had all of the CPU's
> pegged at 100% on a server that usually runs no higher than 10%. Our site
> was not exceptionally busy, nor have we installed anything new that
> accesses
> the database recently. In the sQL Server Error Log I see alot of "buffer
> latch errors", but they appear to have occurred after CPU usage had
> already
> hit 100%.
> No one here is really a SQL Server troubleshooting or tuning expert. What
> should we do to try to determine the cause?
> Thank you
>
|||Try this product eval:
http://www.teratrax.com/tpm/index.html