Continuous Integration and Delivery for Databases

on YouTube ↗01h 00m

" summary

Claim: CI/CD for databases is practical and necessary, but requires explicit migrations, tooling, and staged rollouts. Demonstration uses Roundhouse to add a PetName column, runs local dev DB migrations, green CI build, and an Azure release that runs migrations as a deployment task via Azure Pipelines, with scripts hashed to prevent accidental re-runs. Alternatives discussed include Redgate SQL Change Automation and EF migrations. Operational lessons: expect long-running index or batch jobs, use dual writes/triggers and batched backfills, and plan multi-step zero‑downtime migrations; one migration demo shows version 50 deployed successfully.

AI-written summary · about

" chapters (19)

1. 0:00Start
2. 5:40Desired State Configuration
3. 11:15RedGate SQL Change Automation
4. 12:16Roundhouse Migrations
5. 34:49Example: Table
6. 35:20Example: Column
7. 37:31CREATE OR ALTER
8. 38:58Renaming a table
9. 39:42Splitting a column
10. 40:35Splitting a table
11. 45:13Dual Writing
12. 46:47What about existing data?
13. 48:36Update Read Paths
14. 49:28Update Write Paths
15. 50:42Large Table Migrations
16. 54:23Microservices?
17. 55:39NoSQL Migration Options
18. 57:04Separate transactional from historical
19. 58:19Parting Thoughts

" related talks

• 50mBringing DevOps to the DatabaseSteve Jones · SQL Server Virtual Conference 2021
• 45mEnabling Continuous Delivery with Database PracticesPramod Sadalage · Agile Singapore Conference 2016
• 01h 00mLet's Get Scary and Continuously Deploy Database Changes!Dan Mallott · NDC Oslo 2023
• 46mA Database DevOps PipelineRob Richardson · Øredev 2022
• 46mDatabase DevOps - It is Possible!Stephanie Herr · DevOps World | Jenkins World 2019 San Francisco
• 01h 10mContinuous Integration for the BI DeveloperWolfgang Strasser · Global Azure 2021
• 56mDeploying Docker for Database DevOps DominanceDaniel Mallott · NDC Sydney 2020
• 05mMaking Database Changes a Tier one ArtifactRobert Reeves · swampUP 2017