SQL Server 2025 introduces a new sys.dm_os_memory_health_history view to make it easier for meatbags like you and robots like Copilot to know if the SQL Server has been under memory pressure recently.
To show how it works, let’s run a bunch of simultaneous high-memory-grant queries in the Stack Overflow database:
SELECT TOP 101 * FROM dbo.Users ORDER BY Reputation DESC;
Those of you who have been through my query tuning classes will understand why that query produces particularly high memory grants. I’ll run several of them simultaneously in different sessions, and then check to see what queries are running using