Bringing DevOps to the Database
summary
Claims that databases can be builds tests and releases like app code by putting DDL/DML into Git, running Azure DevOps pipelines for CI, using tSQLt unit tests and a curated data set, and automating releases to QA/staging/prod (demo shows CI failing on a missing primary key then passing after fix). Compares comparison vs migration scripts (pros/cons of SQL Compare style state sync versus ordered migration files) and stresses consistent environments, rollout automation, and selective manual rollback.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:16Three Takeaways
- 2:25What is DevOps?
- 9:19The Application Development Pipeline
- 10:48The Database Development Pipeline
- 14:07Evolving Database Development
- 22:26Database Continuous Integration
- 24:37Database Testing
- 31:55Generate the Update Script
- 33:14Model/State/Compare based process
- 34:18Migrations based process
- 38:03Deploy the Code
- 43:11Release Issues - Rollback
- 45:23Release Issues - Environmental Data
- 48:49Summary
related talks
01h 00mContinuous Integration and Delivery for Databases
36mUnlocking the Benefits of Database DevOps and Automation
27mDevOps and the Database Bottleneck
56mDeploying Docker for Database DevOps Dominance
46mA Database DevOps Pipeline
31mDevOps Practices for the Database Team
01h 00mDevOps for Your Relational Database Foundations
46mDatabase DevOps - It is Possible!
