Let's Get Scary and Continuously Deploy Database Changes!
summary
Shows how to automate database changes in CI/CD with concrete tools and pitfalls: uses SSDT (state‑based) and Flyway (migration‑based) against Azure SQL, keeps seven days of backups, and prefers to roll forward not restore. Demonstrates renaming a table with SSDT requires copy-to-temp and two scripts to preserve rows, while Flyway applies an ordered migration quickly. Describes a custom migration tool that allows out‑of‑order pull‑request deployments, supports 6–8 deployments per day, and avoids destructive rollbacks.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:48Agenda
- 2:53Automation
- 4:22Data is a problem
- 7:27Data stores
- 7:54transactional databases
- 12:19safe changes
- 14:17dropping changes
- 16:34naming changes
- 17:17Renaming a column
- 18:59Renaming a table
- 21:36Protecting against broken business logic
- 22:39Unit testing is your friend
- 24:47Stack Overflow example
- 26:38Time Check
- 27:24Managing Database Source Code
- 30:18Why are we always rolling forward
- 32:49Item potency
- 33:48SQL Server Data Tools
- 47:34Rename
- 49:11State Changes
- 53:34Running the Migration
related talks
01h 00mContinuous Integration and Delivery for Databases
48mApplying effective Source Control to your Database System
50mBringing DevOps to the Database
46mDatabase DevOps - It is Possible!
45mEnabling Continuous Delivery with Database Practices
31mDevOps Practices for the Database Team
01h 00mDevOps for Your Relational Database Foundations
56mDeploying Docker for Database DevOps Dominance