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.
When I first began working with databases, I was lucky to land a job at a little start-up which had solid development and operations processes: all our code, including database code, was in version control. We had a strong database architect who instilled good coding practices into the way we managed database code as well: code was expected to be reusable whenever possible.
In this 70 minute livestream recording, I kick the tires of a fresh new Azure DevOps demo environment showing Redgate’s Hybrid Model for SQL Source Control and SQL Change Automation.
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.
Building your database code is an essential practice to ensure that it compiles from source and that dependencies are met. But things can get tricky when you have objects in some databases which is dependent upon objects in other databases: or even circular dependencies.
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.
I recently set up Redgate’s SQL Change Automation in Visual Studio 2017, and I ran into a confusing error when I started trying to use it. For any other folks out there searching on “Unknown SQL Server Platform,” here’s how I got past it.
Spoiler: Visual Studio suggested updating Microsoft’s SQL Server Data Tools, which failed for me and wasted a lot of time. Updating Visual Studio did fix my issue.
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.