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

Redgate and Rome

By

I’m at the UK Redgate office today, meeting with senior leaders in all areas...

Quick Tip: Check Most DTU Expensive Queries in Azure SQL Database

By

Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...

PowerShell Newbie – Variables

By

This is Week 2 of PowerShell Strikes Back – a four-week May series for...

Read the latest Blogs

Forums

SSRS Is Dead. Here Are Your Real Options

By sgharlow

Comments posted to this topic are about the item SSRS Is Dead. Here Are...

The Distance Metric

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Distance Metric

The New Wave of Security Threats

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The New Wave of Security...

Visit the forum

Question of the Day

The Distance Metric

In the new VECTOR_DISTANCE() function in SQL Server 2025, the first parameter is the distance_metric. What is this?

See possible answers