<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SQL on Damien GOEHRIG</title><link>https://damiengoehrig.ca/tags/sql/</link><description>Recent content in SQL on Damien GOEHRIG</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Damien GOEHRIG</copyright><lastBuildDate>Fri, 26 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://damiengoehrig.ca/tags/sql/index.xml" rel="self" type="application/rss+xml"/><item><title>dbt: Treating Your Data Transformations Like Infrastructure</title><link>https://damiengoehrig.ca/blog/dbt-data-infrastructure-as-code/</link><pubDate>Fri, 26 Dec 2025 00:00:00 +0000</pubDate><guid>https://damiengoehrig.ca/blog/dbt-data-infrastructure-as-code/</guid><description>&lt;p&gt;Snowflake is fundamentally SQL-first. That&amp;rsquo;s its strength: everything is driven by SQL, from grants to object creation to transformations. Infrastructure, we&amp;rsquo;ve seen how to tame it with Terraform in &lt;a
href="https://damiengoehrig.ca/blog/snowflake-terraform-infrastructure-as-code/"&gt;the previous article&lt;/a&gt;. But data transformations fall into a blind spot. SQL scripts scattered everywhere, no tests, no serious versioning, one colleague who knows what order to run things in.&lt;/p&gt;</description></item></channel></rss>