Database Deployment Cowboys to Continuous Delivery Heroes
summary
Organization automates database migrations by storing numbered SQL scripts in source-controlled scripts, running them with a DBUp runner packaged and executed by Octopus Deploy and built by TeamCity. Deploy time drops from eight hours of manual work to about ten minutes and release cadence moves from monthly to weekly. DBA keeps review responsibility but no longer runs production scripts manually. Result is repeatable, transparent deployments, far fewer production breaks, and a preference to roll forward with fixes rather than rollback.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:23Questions
- 1:55Previous Experience
- 2:31About Me
- 4:04Agenda
- 5:11My story
- 5:23My background
- 6:40How it started
- 15:08Better process
- 16:38Route
- 18:55Trust
- 28:53Committing
- 31:13Deploy
- 38:43Recap
- 43:58Rollback
related talks
45mEnabling Continuous Delivery with Database Practices
46mDatabase DevOps - It is Possible!
01h 00mContinuous Integration and Delivery for Databases
23mCD for DBs: Database Deployment Strategies
11mLightning Talk: Continuous Delivery…except for Database Changes
50mBringing DevOps to the Database
31mDevOps Practices for the Database Team
01h 00mLet's Get Scary and Continuously Deploy Database Changes!