Fabric SQL DB critical CI/CD sync issue

[IanBasilioMMM]

I have a SQL DB inside a fabric workspace and I am setting it up for CI/CD using GitHub. But any sync made via the repository fail when syncing to the workspace.

Here are the steps I do:

1. The SQL DB was created within the fabric workspace and the SQL DB works fine on fabric service
2. SQL DB is commited to my repo via the worksapce source control pane
3. I make a simple change to a SQL query via git in the repository
4. I update the workspace items based on the repository changes
5. I get this error: SQL Project build failed. The model version 'SqlDbFabric' is not supported. The model version 'SqlDbFabric' is not supported.

And even if I don't make any changes to the repo I get the error:

1. The SQL DB was created within the fabric workspace and the SQL DB works fine on fabric service
2. SQL DB is commited to my repo via the worksapce source control pane
3. I create a new blank workspace in fabric
4. I sync the workspace with the same branch from my repo that I commited in step 2, basically getting the items from the repo to the workspace
5. I get this error: SQL Project build failed. The model version 'SqlDbFabric' is not supported. The model version 'SqlDbFabric' is not supported.

Is fabric not cabaple of rebuilding the SQL DB from its own created files? Because the documentation says otherwise.

Here is the .sqlproj code autogenerated by fabric:

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build">
  <Sdk Name="Microsoft.Build.Sql" Version="2.1.0" />
  <PropertyGroup>
    <Name>ACTIVITIES_SQL_DB</Name>
    <ProjectGuid>{00000000-0000-0000-0000-000000000000}</ProjectGuid>
    <DSP>Microsoft.Data.Tools.Schema.Sql.SqlDbFabricDatabaseSchemaProvider</DSP>
    <ModelCollation>1033, CI</ModelCollation>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.SqlServer.Dacpacs.DbFabric">
      <SuppressMissingDependenciesErrors>False</SuppressMissingDependenciesErrors>
      <DatabaseVariableLiteralValue>master</DatabaseVariableLiteralValue>
      <Version>170.0.0</Version>
    </PackageReference>
  </ItemGroup>
  <Target Name="BeforeBuild">
    <Delete Files="$(BaseIntermediateOutputPath)\project.assets.json" />
  </Target>
</Project>

[Prince0011]

Based on the information you've shared, this doesn't appear to be an issue with your SQL project or repository.

The key indicator is the error:

SQL Project build failed. The model version 'SqlDbFabric' is not supported.

Your .sqlproj file is generated by Fabric itself and references the Fabric-specific schema provider (Microsoft.Data.Tools.Schema.Sql.SqlDbFabricDatabaseSchemaProvider). Since the failure occurs even with an unmodified project and when syncing to a brand-new workspace, it strongly suggests the Git sync/build service isn't recognizing the SqlDbFabric model version rather than there being an issue with your project.

This is most likely a product limitation or a service-side issue.

I recommend:

• Verifying that both workspaces are on the same Fabric capacity and have the same preview features enabled.

• Avoiding manual modifications to the generated .sqlproj file.

• Opening a Microsoft Support ticket and including the workspace ID, repository details, the generated .sqlproj, and the reproducible steps you've documented.

If Microsoft Support identifies the root cause or provides a workaround, please consider sharing it here so it can help others facing the same issue.

If you found this reply helpful, please consider giving it a Kudos. If it resolves your question or points you in the right direction, marking it as the Accepted Solution will also help other community members find the answer more easily.

[v-prasare]

We are following up once again regarding your query. Could you please confirm whether you have created support ticket?
if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[drew-sk]

hi @IanBasilioMMM - this behavior is very unexpected, there shouldn't be a build error when no changes have been made since the code was synced - and modifying a query shouldn't cause that error either.

We'll need more diagnostic info to get to the root cause, so my suggestion is to open a support ticket - 

https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

You can explore validating your SQL project locally by running "dotnet build" from the terminal in the folder, or by using the VS Code SQL projects extension to run build - but there's nothing in that sqlproj file that would fail the build.