DevOps Source Control not tracking changes in data warehouse

[KPInapple]

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.

[Anonymous · Accepted solution]

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.

[Anonymous]

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.

[dzav]

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.

[Anonymous · Accepted solution]

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.

[Anonymous]

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.

[Anonymous]

Hi @KPInapple ,
Just checking in — did the solution provided help resolve your issue?
If yes, please consider marking it as the accepted answer so it can help others facing a similar challenge.
Thank you.

[Anonymous]

Hi @KPInapple ,

I hope the suggested solution worked for you. If your issue is resolved, kindly accept the post as a solution — it helps the community identify helpful answers more easily.

Thank you.

[dzav · Accepted solution]

This is still an issue for us. However, I discovered that if I make any changes in the service directly even if it's not technically a change - i.e. scripting a create or alter view with no changes - this allows DevOps to pick up all the code changes that were made since the last commit. It looks like any change that we make in SSMS aren't being picked up by source control. We tested this in both SSMS 20 & SSMS 21.