Performance

Investigating the Cause of SQL Server High CPU Load Conditions When They Happen

  • Article

Any DBA who is trying to find the cause of an intermittent problem with a server or database dreams of being able to use a query or procedure take a snap of the relevant variables at the point when the problem occurred. Laerte takes an example of a slow-running query hogging resources to show that you can run queries when a WMI alert is fired, and save the results for later inspection, whenever it happens.

2017-09-20

4,188 reads

Blogs

Using Framing for a Running Total–#SQLNewBlogger

By

Another post for me that is simple and hopefully serves as an example for...

Accessibility in your PowerPoint slide deck

By

This post is part of the series I kicked off here. You can read...

Daily Coping 28 Jul 2021

By

I started to add a daily coping tip to the SQLServerCentral newsletter and to...

Read the latest Blogs

Forums

Error shrinking database

By Ram

While trying to shrink a database using the command "dbcc shrinkdatabase ([db_name])", I get...

Are Powerplans still relevant for VM servers?

By WebTechie

Hello, I am rolling out a new monitoring environment.  While in testing, it is...

SELECT records from table 1 that does not exist in table 2 via UNION

By technoob

Sorry if this seems too beginner; I have been stuck at this for days...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers