A little history of my career as a startup founder of a database change management tool called ReadyRoll.

A collection of blog posts and articles/documentation I've written on database delivery over the last decade or so.

Some of the key takeaways from this blog series on defending against drift in the database delivery pipeline.

If you expect that your environment will be affected by drift at some point, you might be starting to think about next steps. In this post I'll look at the pros and cons of two vastly different approaches to the problem.

This post addresses the underlying causes of drift, including the various risk factors that make a deployment pipeline become prone to drift and ultimately lead to release failure.

One of the most important aspects of adopting automated database deployment is keeping test environments in-synch with the Production environment. However, as we will see, bad things happen when not everyone is on board with using the delivery pipeline.