Steve Jones and I had a great time today talking about source control for databases and release patterns for performance and availability in Seattle. We had a group of folks who asked terrific questions, made thoughtful comments, and interacted throughout the day.
I’m excited for Redgate’s new SQL Change Automation plugin for SQL Server Management Studio (SSMS).
SQL Change Automation lets DBAs and developers use a migrations-first approach to create precise scripts to apply changes to your database. If you’re curious about what I mean by “migrations-first”, read more about this approach, and how it compares to a state-first approach here.
I’m excited to be teaching a full day session with Steve Jones at the SQL PASS Summit on Tuesday, November 5, in Seattle.
Steve and I will be discussing proven patterns to version and deploy changes successfully.
Read more about this precon session, or check out the video below where I give a brief overview of what Steve and I will cover.
I love breaking technology.
I love breaking technology on purpose, in a place where it’s not going to slow anyone else down. It’s a great way to learn more about how everything works and what your options are to fix the situation when things go sideways.
One controversial topic in database development is how to properly store and deploy database changes.
This is generally described as choosing between two options, which are approximately as easy to understand as Greek philosophy:
Sometimes you need to script out all the indexes in a database. Maybe you’re concerned something has changed since they were last checked in. Or maybe the indexes aren’t checked into source control, and you’re working on fixing that. (Important!)
Either way, sometimes you need to do it, and it’s not fun through the GUI. I needed to write some fresh demo code for this recently, and I needed it to give the details for partitioned tables using data compression, and I thought I’d share.
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.