Events
Mar 31, 11 PM - Apr 2, 11 PM
The ultimate Microsoft Fabric, Power BI, SQL, and AI community-led event. March 31 to April 2, 2025.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This article explains how Git integration and deployment pipelines work for warehouses in Microsoft Fabric. Learn how to set up a connection to your repository, manage your warehouses, and deploy them across different environments. Source control for Fabric Warehouse is currently a preview feature.
You can use both Git integration and Deployment pipelines for different scenarios:
Git integration in Microsoft Fabric enables developers to integrate their development processes, tools, and best practices directly into the Fabric platform. It allows developers who are developing in Fabric to:
For more information on the Git integration process, see:
From the Workspace settings page, you can easily set up a connection to your repo to commit and sync changes.
The following image is an example of the file structure of each warehouse item in the repo:
When you commit the warehouse item to the Git repo, the warehouse is converted to a source code format, as a SQL database project. A SQL project is a local representation of SQL objects that comprise the schema for a single database, such as tables, stored procedures, or functions. The folder structure of the database objects is organized by Schema/Object Type. Each object in the warehouse is represented with a .sql file that contains its data definition language (DDL) definition. Warehouse table data and SQL security features are not included in the SQL database project.
Shared queries are also committed to the repo and inherit the name that they are saved as.
With the SQL Database Projects extension available inside of Azure Data Studio and Visual Studio Code, you can manage a warehouse schema, and handle Warehouse object changes like other SQL database projects.
To download a local copy of your warehouse's schema, select Download SQL database project in the ribbon.
The local copy of a database project that contains the definition of the warehouse schema. The database project can be used to:
To publish the warehouse schema to a new warehouse:
You can also use deployment pipelines to deploy your warehouse code across different environments, such as development, test, and production. Deployment pipelines don't expose a database project.
Use the following steps to complete your warehouse deployment using the deployment pipeline.
For more information about the Fabric deployment pipelines process, see Overview of Fabric deployment pipelines.
ALTER TABLE
to add a constraint or column in the database project, the table will be dropped and recreated when deploying, resulting in data loss. Consider the following workaround to preserve the table definition and data:
CREATE TABLE
and INSERT
, CREATE TABLE AS SELECT
, or Clone table.ALTER TABLE
.DataflowsStagingWarehouse
that appears in the repository.ALTER TABLE
to add a constraint or column in the database project, the table will be dropped and recreated when deploying, resulting in data loss.DataflowsStagingWarehouse
that appears in the deployment pipeline.Events
Mar 31, 11 PM - Apr 2, 11 PM
The ultimate Microsoft Fabric, Power BI, SQL, and AI community-led event. March 31 to April 2, 2025.
Register today