Unveiling the magic of CI/CD for SQL Server using GitHub Actions
summary
Follows a concrete CI/CD recipe: build SQL Server database projects in Azure Data Studio, create SDK-style database project (globbing), run YAML workflows on GitHub Actions, and deploy either state-based DACPACs or migration scripts via dbops PowerShell module and DBUp. Covers self-hosted vs GitHub-hosted runners (standard image ≈ 2 CPUs), cost differences (Ubuntu 1× minute, Windows 2×, macOS much higher and runs only in the US), secret storage (GitHub Secrets or Azure Key Vault), and TSQLT unit tests with an automatic test-generator; demos run end-to-end.
AI-written summary · about
chapters (16)
- 0:00Session introduction
- 1:01Agenda overview
- 2:23Speaker bios
- 3:53Speaker bios continued
- 5:33Git branching strategies
- 11:25Tools and integration
- 12:12GitHub browser demo
- 16:44GitHub runner configuration
- 20:44SQL Server deployments
- 29:35Migration-based deployment
- 31:37Managing secrets
- 34:18Database unit testing
- 37:05Audience Q&A
- 40:08GitHub actions deep dive
- 42:11GitHub script automation
- 44:03Metrics and conclusion
related talks
49mUnveiling the magic of CI/CD for SQL Server using GitHub Actions
44mCI/CD with GitHub Actions
48mConnecting the dots of Azure SQL DevOps
48mCICD with Github Actions
48mGitHub + Azure: Better Together!
36mEnabling DevSecOps best practices with GitHub Actions
56mCI/CD and beyond with GitHub Actions
50mA Deep Dive into DevOps Practices with Azure SQL