Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered

Reply
KPInapple
New Member

DevOps Source Control not tracking changes in data warehouse

DevOps Source Control has not tracked any changes made in the data warehouse for the last month. It's not working for views or tables.

4 REPLIES 4
v-pagayam-msft
Community Support
Community Support

Hi @KPInapple ,
Can you please confirm whether you have resolved issue. If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.

v-pagayam-msft
Community Support
Community Support

Hi  @KPInapple ,
Thank you for reaching out to us on Microsoft Fabric Community Forum!

Currently, DevOps source control for Fabric Warehouse is in preview and has known limitations:

It may not track individual changes (like table or view modifications). Instead, it commits the entire warehouse as a single JSON object.

This means schema-level changes might not be visible in Git history granularly.

 For more information, please refer to the following links:
https://learn.microsoft.com/en-us/fabric/data-warehouse/source-control
Refer Community thread which might help you:
https://community.fabric.microsoft.com/t5/Data-Warehouse/Warehouse-git-integration-and-dbt/m-p/43338...

Regards,
Pallavi G.

Hi Pallavi, even if it's not granular, shouldn't it reconize that a change has been made to the warehouse? If view and table changes aren't being recognized as a change, what would trigger DevOps to recognize a change in the warehouse?

 

EDIT: additionally, this was something that was working about a month ago. I have a change from May 15th that was recognized but nothing since then.

Hi @dzav ,
You may normally see at least a change recognized at the warehouse level when something is updated, even if it’s not granular down to each table or view.I’d suggest double-checking the Source Control configuration and adding a small change to see if it gets recognized , that might help to determine whether it’s a one-time miss. 

Thank you.

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June FBC25 Carousel

Fabric Monthly Update - June 2025

Check out the June 2025 Fabric update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.