Ever had a database change go horribly wrong? It can feel awful in the moment, then eat away at your confidence for days afterward.
In this 20 minute episode, I give you practical steps that help you cope with change over the course of your DBA career.
I had a fun highlight recently that I wanted to share. I’ve got a new poster idea I’m crazy about.
The dev server got bogged down during a deployment and lock timeouts were everywhere. Was the perfmon counter way off about how much memory was being used just for locks?
As I’ve gotten back into the swing of a more-or-less regular work schedule after the initial launch of SQL Workbooks, I’ve revived some of my favorite work habits and free tools.
I’m a big fan of the time-tracking tool Toggl. Their tools are easy to use, and even the free version is very cool.
Tracking time may seem like a giant pain if you’re used to using terrible tools for it. But Toggl is simple, and it helps keep me sane.
A database transaction log is expanding, even though the DBA is running log backups and doesn’t see an open transaction? What’s going on with this Availability Group?
I’ve started up a weekly newsletter! Sign up, and each Tuesday you’ll get a link to a quick SQL Server quiz or poll in your inbox. Most weeks there will be a cartoon thrown in there, too.
A few episodes ago, I talked about how learning about Write Ahead Logging was a light bulb moment for me, and helped me learn tons of concepts about backups and recovery.
This week, we talk about when SQL Server turns things upside down and doesn’t use write ahead logging: and what it has to do for recovery in these special cases.
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.