Forum Discussion
Fabric SQL Database and Visual Studio Project
Hi DebbieE
If I've understood you correctly, to deploy SQL changes into a Fabric SQL Database that is under source control, you should use the Fabric deployment flow. Change your database code, commit to git (if necessary PR into fabric's branch), then use Source Control => Updates => “Update all” in Fabric UI. Then the item state is applied to the SQL Database.
I guess it publish a SQLproj directly to Fabric SQL Database is not always working ideally, although you could use SqlPackage.exe (with /p:AllowIncompatiblePlatform=true)
I recommend checking this page: SqlPackage for SQL database - Microsoft Fabric | Microsoft Learn and this one: Fabric SQL database source control integration - Microsoft Fabric | Microsoft Learn
Hope that helpsOnur
😊If this post helped you, feel free to give it some Kudos! 👍
✅And if it answered your question, please mark it as the accepted solution.
I had build issues and I was using the new DSK which changes thing so with a bit of rework on the sdk project file its now building but seeminly you cant deploy to the database in the same way you can with an Azure SQL Database. there seems to be an isue working with DACPAC's which is a roadblock that feels like a gap in the GA release.
Here’s the situation:
- I created a SQL Database Project using the new Database SDK (DSK).
- After some adjustments to the SDK project file, I successfully built the project and generated a DACPAC.
- Naturally, I expected to deploy this DACPAC to my Fabric Database the same way I would with Azure SQL Database using sqlpackage /a:Publish.
The problem:
Fabric Database does not currently support DACPAC deployment. There’s no way to publish directly from SSDT or DevOps pipelines using the standard DACPAC workflow. The only workaround is to extract the schema scripts and run them manually or automate custom scripts against the Warehouse SQL endpoint.
This breaks the normal CI/CD pattern for database projects and makes Fabric feel incomplete at this level. For enterprise workflows, DACPAC support is critical.
Questions:
- Is DACPAC deployment on the roadmap for Fabric Database?
- Will Fabric achieve parity with Azure SQL for schema deployment and CI/CD?
- Are there any official migration tools or recommended approaches beyond manual script execution?
Hi DebbieE, I did testing and confirm that DACPAC deployment using Publish in the Database project in VS Code from a remote computer works for Fabric SQL database with no issues. I ran a full experiment in Fabric to research your scenario and my confirmation is solid: you can use a Database project created by Fabric and committed to Git on a remote computer with the correct SSDT (in my case Database project extension in VS Code) to publish changes directly to Fabric SQL database. I can provide more information with the specific steps and screenshots in another post if you need that.
The outstanding question remains: can I use sqlpackage to deploy a DACPAC built in VS Code directly to a Fabric SQL database? I am going to test that next and will report my answer here.
