<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SQL Server on ArcticDBA - Alexander Arvidsson</title>
    <link>/tags/sql-server/</link>
    <description>Recent content in SQL Server on ArcticDBA - Alexander Arvidsson</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/sql-server/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>That One SQL Server Outage I&#39;ll Never Forget</title>
      <link>/posts/t-sql-tuesday-202/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/t-sql-tuesday-202/</guid>
      <description>Back in 2015, I was debugging a SQL Server cluster that worked perfectly. Except when it didn&amp;rsquo;t. Connections timed out randomly, failovers failed silently, and nothing made sense. I was sure it was DNS. It was DNS. But that wasn&amp;rsquo;t the real problem. The real problem was me, seeing exactly what I expected to see instead of what was actually there. Turns out, pilots and DBAs have something important in common: expectation bias can really mess you up.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/t-sql-tuesday-202/cover.jpg" />
    </item>
    
  </channel>
</rss>
