Blog Post

Fabric Updates Blog
4 MIN READ

Why your database schema belongs in Git

iqrashaikh's avatar
iqrashaikh
Icon for Microsoft Employee rankMicrosoft Employee
5 months ago
Author: Iqra Shaikh - Product Manager 2 At SQLCon this year, a room full of SQL developers was asked two questions. How many already have their databases under source control? Some hands went up. ...
Updated 5 months ago
Version 2.0
Databases
developer
fabric platform
microsoft fabric
YevgenyM's avatar
YevgenyM
Icon for Advocate IV rankAdvocate IV
4 months ago

Hi iqrashaikh

How to implement similar approach with Fabric Lakehouse?
We have feature branch(1..n) ➡️ Dev ➡️ UAT ➡️ PROD

We do all our changes in the feature branches (in Fabric notebooks)
(never touch the Dev/UAT/Prod directly except for Database schema changes)

Specifically, I would like to know how do you make sure the process apply the change only once per stage and without data loss (at any point).