This post is part of TSQLTuesday #140, “What have you been up to with containers?”
Disposable databases are indispensable for software developers, both for initial development work and in automation pipelines. Containers pair exceptionally well with temporary databases and provide a lightweight mechanism to spin up an environment on demand.
When I woke up today in the UK, Twitter was alive with jokes, hot takes, and sympathy about an email sent out to millions of folks on a contact list for HBO Max featuring the subject line, “Integration Test Email #1”.
One big gotcha that teams often encounter when automating deployments for databases is that it’s difficult (or sometimes impossible) to ensure that all changes to the production database are performed through the automation pipeline.
These out-of-band changes case the production database to “drift” away from the schema as defined in version control.
Many people use entrenched processes for database development that have been in place so long that it’s hard to imagine doing it any other way. In this episode, I share three things that should NOT be normal for database development– but which are incredibly common.
Learning Git can be daunting for DBAs. In this 20 minute episode, I discuss why learning a VCS is necessary for DBAs, then give three tips on scoping your project, choosing the right tools, and making sure the project is successful.
I believe that language matters, and that it is worth our effort to move away from language associated with slavery and racism whenever possible.
I used to make fun of YAML because I was scared of it. I still make fun of YAML, but I’m not scared of it anymore now that Rob Sewell showed me how to avoid having to write it myself.
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.