Applying effective Source Control to your Database System
summary
Demonstrates using SSDT (Visual Studio) to keep schema in source control, build a dacpac and deploy it through an Azure DevOps pipeline that creates the database when missing, compares definitions to decide create vs alter, and runs post-deployment scripts to apply seed-data migrations. Demo deploys to local SQL Server 2022 instances, shows the pipeline building an artifact, registering migration IDs, and inserting four county rows. Notes: SSDT won’t auto-drop objects or shorten columns safely — use pre/post scripts for destructive changes.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:48SQL process problems
- 4:40SQL Server Data Tools
- 12:15Demo overview
- 15:27Basic table with audit
- 17:14Schema migrations and seed data
- 21:52Deploy from Visual Studio
- 26:07Post-deploy scripts and tracking
- 30:10Branching in Azure DevOps
- 33:01Commit changes and PRs
- 36:16CI/CD for database
- 38:49Handling object removal
- 42:24Branching strategies
- 44:52Users and permissions in SSDT
- 45:55Q&A
related talks
01h 00mDevOps for Your Relational Database Foundations
01h 00mLet's Get Scary and Continuously Deploy Database Changes!
50mA Deep Dive into DevOps Practices with Azure SQL
01h 12mNext-gen SQL Projects with Microsoft.Build.Sql
01h 09mAzure SQL Database Development Inner and Outer Loops
45mSQL Projects for Database Development
50mBringing DevOps to the Database
20mExcellent Database Adventure: From Code Errors to Reliable Releases