Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
DevOps Flow Series, part 4 of 4
Zero downtime database deployments
You understand that big bang deployments are painful, but
each deploy may disrupt users, so you are restricted to
tight deployment windows for your database. The consequences
of missing your windows aren't worth thinking about - but it
gets more difficult each time.
In order to move to smaller, more frequent and more reliable
deployments you need to demonstrate that you can safely
deploy during business hours - without disrupting users.
In this session we'll discuss the most popular strategies:
Blue/Green and Canary deploys, Cluster Immune Systems and
Feature Toggles. Then we'll discuss the fundamental changes
that we need to make to the way we think about database
"deployments" and "releases" in order to support these
We will finish with a SQL Server demo that simulates the
Facebook Chat case study from The DevOps Handbook. The
principles will be applicable to any relational database
deployment, regardless of tooling.
Short description
Moving to a safer release cadence, based on smaller, more
frequent deployments, normally requires deployments to occur
while the systems are running. That’s scary. In this session
we’ll discuss how to do it safely.
More from the DevOps Flow series:
1. DevOps 101 for Data Folks:
2. Simple database deployments with GitHub, Azure DevOps Services and SSDT:
3. Solving the dev database problem with GitHub, Docker and dbaclone:
4. Zero downtime database deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.