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

Reflections on the Life of a DBA

By

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

Moving On-Prem PostgreSQL to the Cloud: Picking the Right Path for Big Tables

By

Every PostgreSQL migration eventually hits the same fork in the road. The database is...

A Spread of Vacation

By

I’m off on vacation today. Which is a little weird as I just got...

Read the latest Blogs

Forums

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...

TempDB Facts I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item TempDB Facts I

Visit the forum

Question of the Day

TempDB Facts I

Can I set Accelerated Database Recovery on tempdb?

See possible answers