<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deep Dive on StraightforwardSQL</title>
    <link>https://straightforwardsql.com/categories/deep-dive/</link>
    <description>Recent content in Deep Dive on StraightforwardSQL</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Aug 2024 16:09:14 +0200</lastBuildDate><atom:link href="https://straightforwardsql.com/categories/deep-dive/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Service Broker Blocking</title>
      <link>https://straightforwardsql.com/posts/service-broker-blocking/</link>
      <pubDate>Fri, 09 Aug 2024 16:09:14 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/service-broker-blocking/</guid>
      <description>I was paged for a blocking chain where the lead blocker had a transaction name I&#39;d never seen: CSbRollbackHandlerTask::DisableQ. Here is how I reproduced it and why the blocked process report refuses to help.</description>
    </item>
    
    <item>
      <title>Async stats update causing blocking</title>
      <link>https://straightforwardsql.com/posts/async-stats-update-causing-blocking/</link>
      <pubDate>Sun, 16 Jun 2024 20:00:27 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/async-stats-update-causing-blocking/</guid>
      <description>An index rebuild quietly blocked an async stats update, and the whole server started timing out. Here is the lock-partitioning repro and the SQL Server 2022 fix.</description>
    </item>
    
    <item>
      <title>Are ABORT_AFTER_WAIT&#39;s victims logged?</title>
      <link>https://straightforwardsql.com/posts/are-abort_after_wait-victims-logged/</link>
      <pubDate>Sat, 18 May 2024 21:10:20 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/are-abort_after_wait-victims-logged/</guid>
      <description>Does ALTER INDEX REBUILD with WAIT_AT_LOW_PRIORITY log its victims in the error log the same way KILL does? Let&#39;s find out.</description>
    </item>
    
    <item>
      <title>Scary Scalar Functions - Part Four: Your Environment</title>
      <link>https://straightforwardsql.com/posts/scary-scalar-functions-your-environment/</link>
      <pubDate>Sun, 02 Oct 2022 20:40:04 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/scary-scalar-functions-your-environment/</guid>
      <description>You&#39;ve learned why Scalar UDFs are slow and how to remove them. The last question: where do you even start? Here&#39;s how I triage them across a whole environment.</description>
    </item>
    
    <item>
      <title>Scary Scalar Functions - Part Three: The Cure</title>
      <link>https://straightforwardsql.com/posts/scary-scalar-functions-the-cure/</link>
      <pubDate>Sun, 24 Jul 2022 11:45:04 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/scary-scalar-functions-the-cure/</guid>
      <description>Nuke them from orbit, or inline them. The practical ways to neutralize Scalar UDF performance pain, from a free SCHEMABINDING win to a full ITVF rewrite.</description>
    </item>
    
    <item>
      <title>Scary Scalar Functions - Part Two: Performance</title>
      <link>https://straightforwardsql.com/posts/scary-scalar-functions-performance/</link>
      <pubDate>Sat, 02 Jul 2022 14:21:57 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/scary-scalar-functions-performance/</guid>
      <description>A Scalar function that does literally nothing still runs over 20 times slower. Here is the proof, measured four different ways.</description>
    </item>
    
    <item>
      <title>Scary Scalar Functions - Part One: Parallelism</title>
      <link>https://straightforwardsql.com/posts/scary-scalar-functions-parallelism/</link>
      <pubDate>Tue, 21 Jun 2022 13:21:35 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/scary-scalar-functions-parallelism/</guid>
      <description>Consultants hate me for this one weird trick. Because I&#39;ll be uncovering all the mess Scalar functions can cause in a series of articles.</description>
    </item>
    
    <item>
      <title>New Extended Events in SQL Server 2022</title>
      <link>https://straightforwardsql.com/posts/new-extended-events-in-sql-server-2022/</link>
      <pubDate>Tue, 24 May 2022 18:33:05 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/new-extended-events-in-sql-server-2022/</guid>
      <description>SQL Server 2022&#39;s CTP has dropped. I diffed its Extended Events against 2019 and pulled out the few new ones worth a look.</description>
    </item>
    
    <item>
      <title>KEEP PLAN Demystified</title>
      <link>https://straightforwardsql.com/posts/keep-plan-demystified/</link>
      <pubDate>Thu, 07 Apr 2022 18:56:37 +0100</pubDate>
      
      <guid>https://straightforwardsql.com/posts/keep-plan-demystified/</guid>
      <description>Ever wondered what the KEEP PLAN hint actually does? The docs are vague, so I tested it against every recompilation threshold to find out.</description>
    </item>
    
    <item>
      <title>Query Store default settings</title>
      <link>https://straightforwardsql.com/posts/query-store-default-settings/</link>
      <pubDate>Thu, 23 Sep 2021 22:03:31 +0200</pubDate>
      
      <guid>https://straightforwardsql.com/posts/query-store-default-settings/</guid>
      <description>Query Store comes with default settings - but are they what the documentation says? Let&#39;s find out using a simple Extended Events session.</description>
    </item>
    
  </channel>
</rss>