<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Query Store on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/query-store/</link><description>Recent content in Query Store on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/query-store/index.xml" rel="self" type="application/rss+xml"/><item><title>Rank Top Memory Consumers with sys.dm_os_memory_clerks</title><link>https://www.sqlserver70.com/post/top-memory-consumers-dm-os-memory-clerks/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/top-memory-consumers-dm-os-memory-clerks/</guid><description>
&lt;p&gt;Buffer pool counters explain data cache pressure but go silent the moment memory trouble comes from somewhere else. &lt;code&gt;sys.dm_os_memory_clerks&lt;/code&gt; is the DMV that covers everything the buffer pool doesn't — plan cache, In-Memory OLTP, Query Store, query memory grants, Extended Events sessions — by reporting &lt;code&gt;pages_kb&lt;/code&gt; per clerk. Grouping those rows by &lt;code&gt;type&lt;/code&gt; produces a ranked list of exactly which internal SQL Server subsystem is holding the most memory right now.&lt;/p&gt;</description></item></channel></rss>