External Article

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

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.

Blogs

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

T-SQL Tuesday #200: When I Look at a Query …

By

This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...

Reflections on the Life of a DBA

By

The DBA life is fraught with pain. Those battles that we endure are mostly...

Read the latest Blogs

Forums

cons for a dev machine in a different version of sql from our prod server

By stan

hi, im not a dba. For a couple of years our dev sql server...

Inquiry – Enforcing ApplicationIntent=ReadOnly via GPO

By abdalah.mehdoini

Hello, I would like to ask whether it is technically possible to redirect a...

Calculating Geometric Mean in Power BI

By Dinesh Asanka

Comments posted to this topic are about the item Calculating Geometric Mean in Power...

Visit the forum

Question of the Day

TempDB Facts I

Can I set Accelerated Database Recovery on tempdb?

See possible answers