July 13, 2011 at 7:02 am
If CPU goes high, what all analysis a DBA has to do?
July 13, 2011 at 9:34 am
Are you sure it is a process within SQL Server using high amounts of CPU? What else is running on the server?
If you're sure you're supposed to be looking at SQL Server see Tip 3 in this article and look to tune queries with high "Average Worker Time" and "Total Worker Time" counts. Be mindful that sometimes tuning a query with a middle-of-the-road "Average Worker Time" but a high "Total Worker Time" can have a big impact on improving your overall system as well:
http://www.sqlmag.com/article/sql-server/top-10-performance-tips-for-sql-server
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 13, 2011 at 9:37 am
I would also check to see if there are scheduled jobs running in SQL Server Agent, perhaps there are some overlapping jobs or a job is running during a time when heavy load is on the server.
July 13, 2011 at 9:46 am
Also check and makes sure all HDs associated with SQL server are not full.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply