<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Index Tuning on Morten Ankerstjerne</title>
    <link>https://mortenankerstjerne.com/tags/index-tuning/</link>
    <description>Recent content in Index Tuning on Morten Ankerstjerne</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Apr 2025 18:49:18 +0200</lastBuildDate>
    <atom:link href="https://mortenankerstjerne.com/tags/index-tuning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Column order matters in Clustered Indexes</title>
      <link>https://mortenankerstjerne.com/posts/2025/index-column-order/</link>
      <pubDate>Sun, 23 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://mortenankerstjerne.com/posts/2025/index-column-order/</guid>
      <description>&lt;p&gt;&lt;em&gt;Demo scripts &lt;a href=&#34;#demo-scripts&#34;&gt;below&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;I recently worked on a problem for a customer who experienced some performance issues with a job on their SQL Server database.&lt;/p&gt;&#xA;&lt;p&gt;Because they use SQL Server Standard Edition, their solution included a home-rolled version of table partitioning, where two tables were created every week:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;one contained 10-second aggregate values, written in microbatches every 10 seconds&lt;/li&gt;&#xA;&lt;li&gt;the other similarly contained 5-minute values, written from the 10 second table every 5 minutes&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;All of these aggregates were based on raw measurements from their various systems, one measurement per device.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
