Git and deployment pipeline limitations of Fabric Data Warehouse

[JoachimH]

When will the current Git and deployment pipeline limitations of Fabric Data Warehouse be fixed? Especially related to data loss due to alter table operations.
https://learn.microsoft.com/en-us/fabric/data-warehouse/source-control#limitations-in-git-integratio...

[arpost]

Good question, @JoachimH. Been contemplating this as there's almost zero way to handle DW deployments using native Fabric tools due to the risk of data loss. Since nothing generates "migration" scripts either, this means we have to do manual ALTER TABLE scripting to sync changes. Creates significant challenges at scale (e.g., 50 tables in 2 DWs).

As of right now, I'm using deployment pipelines to "check in" code to Test so we can do code compare, but pipelines for DWs are basically "dead" until deployments can actually handle data movement. The fact that an accidental deploy could cause data loss makes me sweat bullets...

An additional "complicating factor" is the new IDENTITY feature. Love having this out of the box in DWs, but the fact that it doesn't support SET IDENTITY_INSERT like in a SQL DB means you can never just drop/recreate table and reinsert data and set the IDENTITY values that were already generated before re-enabling IDENTITY behavior. Deployments now require that you ALSO update related tables as DROP/CREATE + INSERT will generate new identity values.

[JoachimH]

Hi @tayloramy ,

Yes, I checked the roadmap. Pretty disappointing... It has been a preview feature for almost 18 months now with no solution in sight.
CI/CD with Warehouses in Microsoft Fabric | Microsoft Fabric Blog | Microsoft Fabric

[v-sshirivolu]

HI @JoachimH ,
As of now, Fabric Data Warehouses are still not fully CI/CD ready for safe, automated production use. While Git integration and deployment pipelines exist, the documented limitations around schema changes, data loss risks, and pipeline behavior mean most teams still rely on DACPAC based or controlled manual deployments. Until Microsoft addresses these gaps with clearer timelines, Warehouses remain only partially suitable for enterprise grade CI/CD.

[v-sshirivolu]

Hi @JoachimH ,

I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

[v-sshirivolu]

Hi @JoachimH ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

[JoachimH]

Hi @v-sshirivolu,

Thanks for following up. However, according to the answers no solution exists, and Microsoft doesn't have one on the roadmap...

[v-sshirivolu]

Hi @JoachimH ,
Thanks for your feedback. Since this feature is still in preview, some limitations are normal. To help improve it, please submit or upvote ideas in the Fabric Ideas forum. Your input is appreciated.

https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideas/ideas/search-ideas

[tayloramy]

Hi @JoachimH, 

I don't see that anywhere on the roadmap right now, these are the Git related features that have a planned implementation date: 

Microsoft Fabric Roadmap