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

Speeding Up Patching – Beyond Patch Delivery

By

I wear many hats in technology, and one of those is as a (cyber)security...

Monday Monitor Tips: Query Recommendations

By

We keep adding stuff to Redgate Monitor, and it’s easy to miss some of...

A Pursuit of Lifelong Learning

By

The following came across my YouTube feed today. It’s an interview with General James...

Read the latest Blogs

Forums

Azure SQL Hyperscale Unveiled

By Site Owners

Comments posted to this topic are about the item Azure SQL Hyperscale Unveiled

What is the worst part about existing monitoring solutions?

By Evgenii Vaniukov

Hi. What is the most difficult aspect of using monitoring software like idera, redgate,...

MiniMax m3 and SQL Server

By Daniel Calbimonte

Comments posted to this topic are about the item MiniMax m3 and SQL Server

Visit the forum

Question of the Day

SQL Server Vector Support I

What are vectors in SQL Server 2025, as related to the new AI features?

See possible answers