<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Warehouse on Morten Ankerstjerne</title>
    <link>https://mortenankerstjerne.com/tags/data-warehouse/</link>
    <description>Recent content in Data Warehouse on Morten Ankerstjerne</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Jun 2025 16:03:26 +0200</lastBuildDate>
    <atom:link href="https://mortenankerstjerne.com/tags/data-warehouse/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stop auto-shrinking your staging database</title>
      <link>https://mortenankerstjerne.com/posts/2025/stop-shrinking-stage/</link>
      <pubDate>Thu, 05 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://mortenankerstjerne.com/posts/2025/stop-shrinking-stage/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;If you&amp;rsquo;ve worked with data warehouse development on Microsoft SQL Server, you have probably had a run-in with your SAN-admin at some point, complaining about the size of your databases, and asking if you can do some cleanup to free up disk space.&lt;/p&gt;&#xA;&lt;p&gt;What often ends up happening is, you take look at the database files and realize there&amp;rsquo;s a lot of free space that could be released, especially if you have a database dedicated to staging transformed data, before loading it into data marts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
