SQL Server Science
Technical Articles for the DBA / Developer
Home » technical-writing

Acronyms, Collisions, and the Cost of Not Asking

2026-08-22 · by Hannah Vernon · in Hot Takes

I promised a follow-up to a post about tech vocabulary,[1] and this is it. That one argued that dramatic words and vague words fail the same way: they carry attitude where information should be. I…

The Blast Radius Was Four Rows

2026-08-20 · by Hannah Vernon · in Hot Takes

A while back I read an incident report that described the “blast radius” of a “catastrophic” data issue. I kept reading, looking for the part where something exploded. The actual damage: four rows in a…

Two Spaces After a Period: The Hill I Will Die On

2026-05-15 · by Hannah Vernon · in Hot Takes

I’m going to say something controversial in the year 2026, and I don’t care who it offends: You should put two spaces after a period. There. I said it. Come at me. The “One Space”…

Search

Categories

  • AI for DBAs
  • announcements
    • events
  • basics
    • localization
  • configuration
  • Data Architecture
  • DMVs
  • documentation
  • extended-events
  • Git for DBAs
  • High Availability
  • Hot Takes
  • Internals
  • maintenance
    • patching
  • Opinion
  • performance
  • PostgreSQL
  • Professional Development
  • recovery
  • reporting
  • ROLLBACK;
  • security
    • data security
  • service broker
  • SQL Server Agent
  • statistics
  • sys
  • t-sql
    • xml
  • tools
    • data masking
    • wsus
  • troubleshooting
  • Uncategorized

Pages

  • About SQL Server Science
  • Get Better Help with a Minimal, Complete, and Verifiable Example, or MCVE
  • Privacy Policy

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.

To find out more, including how to control cookies, see here: Cookie Policy

Copyright © 2026 SQL Server Science