Deploying databases shouldn't feel uncertain. Synchronizing development and production schemas in Microsoft Fabric Warehouse can be challenging as database objects evolve. A frequent issue arises when the .sqlproj file isn't configured with the Fabric-specific schema provider (SqlDbFabricDatabaseSchemaProvider). Misconfiguration may lead Schema Compare to flag supported Fabric objects as unsupported. To avoid this issue, explicitly specify the schema provider in the .sqlproj XML if the GUI does not offer that option.
In this blog, let's take a quick look at how to get started.
Before using Schema Compare with Fabric Warehouse, make sure you have the following prerequisites.
- You need access to an existing Warehouse item within a Microsoft Fabric workspace, with Contributor or higher permissions.
- You also need Visual Studio Code installed on your workstation.
- Next, install the .NET SDK, which is required to build and publish database projects.
- Finally, install these two Visual Studio Code extensions:
- SQL Database Projects
- SQL Server (mssql)
Both extensions are available directly from the Visual Studio Code Marketplace.
After installing the extensions, open Visual Studio Code and select "Add Connection" to connect to Fabric Warehouse.
Enter the required server and authentication details, and complete the connection.
After connecting, access the Warehouse directly in Visual Studio Code.
Open Schema Compare
Now navigate to Database Projects in Visual Studio Code.
You should see your available database projects and connections. Right-click the database project or connection and select "Schema Compare."
Schema Compare gives you an object-level view of the differences between the source and target.
You can compare schemas between:
- .dacpac files
- Databases
- SQL database projects
Comparison results outline actions to align target with source.
Instead of treating the database as a single deployment unit, you can review individual changes and decide what should happen next.
You can also selectively exclude actions from the comparison results when a particular change should not be deployed.
Schema Compare with Fabric Warehouse
Schema Compare's integration with Fabric Warehouse allows developers to identify differences in database objects before implementing changes.
Database Projects and Git
The database project becomes the artifact under review in the PR, not a raw DDL diff — schema changes get the same scrutiny as application code, and the deployment pipeline consumes a validated project state rather than an ad-hoc script.
Schema Compare exposes Fabric Warehouse DDL limitations before deployment, helping you proactively address issues and maintain greater control over the deployment process.
Super User