Udemy

Introduction CI-CD for Database

A free video tutorial from Houssem Dellai
Simplifying Cloud & DevOps for Everyone
Rating: 4.4 out of 5Instructor rating
14 courses
303,140 students
Introduction CI-CD for Database

Learn more from the full course

Learn Azure DevOps CI/CD pipelines

Create CI/CD pipelines for Java, .NET, NodeJs, Docker, Terraform, Nuget, Kubernetes, SQL Server, Bicep and ARM templates

13:51:16 of on-demand video • Updated June 2026

What is DevOps and CI/CD
Creating CI/CD pipelines for Web, Mobile and Container apps
Including the Database into the pipelines
Configure deployment to Azure Cloud
Run unit, functional and load tests as part of the pipeline
Analyse source code using Sonar
Use Infrastructure as Code (IaC) from CI/CD with ARM templates
Use Configuration as Code (CaC) in Azure DevOps
Create Dev-Test-Prod environments
Secure the pipelines sensitive data
Use Infrastructure as Code (IaC) from CI/CD with Terraform
Deploy containers into Kubernetes
English [Auto]
Let's learn how to create the CIA pipeline for a secret server database. For applications that uses a database, we can either use entity framework to manage the database migrations, but lots of users are actually using SSD tools. SQL Server Data Tools. This means they use the database project type and Visual Studio are available also on a systems server management studio. Because this project gives them more flexibility and more control over the scripts that will run the database. Creating the CIA and pipelines for the database now means. Building the this project type this database project another to generate the DEC back file, then deploying that deck back from this steady pipeline. The deck back file is a package that contains the sequel scripts and also the storage procedures for the new schema of the database. So in this time we want to add a table that should go to and to a sequel script, and this script will be included into this attack back file. So from our CIA pipeline, we get that database project. Then we will build it using I must build Tusk because it won't build with botnets, so it'll be using a mass build. So a generator that backfired. Now, later from this pipeline, we'll take that backpack fire from the artifact. Then we'll deploy it into a secret Asia database. We can also connect to any SQL Server database and to deploy that file to update the schema of that database.