I got a question recently about a panel discussion on Database Development Disasters at SQL in the City Streamed. I had framed a question as, “how fast should development go without load or performance testing?”
Redgate is building a library of real-world stories about database development disasters.
Your mission: Tell us a true story in 500 words or less about a time when you were involved in an Agile or DevOps project that went full steam ahead in speeding up delivery of application code, but didn’t modernize database development practices. Did trouble follow? Check out the prizes and give us the scoop here before March 20, 2019.
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.
I’m excited to have just clicked ‘publish’ on four new videos in the brand new Advocate playlist on Redgate’s YouTube channel.
These videos step through setting up and working with a project in one of my favorite Redgate tools: SQL Change Automation.
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:
Next week, I’m giving a free webcast for Redgate on DevOps fundamentals. DevOps is something I am a big proponent of for database administrators, developers, and company leaders.
I’ll cover three points which are often the source of misunderstandings.
I recently participated in a panel discussion for the SQL PASS DevOps virtual chapter.
Watch our discussion about how to make three different teams successful at database DevOps.
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.