Question

A data engineering team maintains a Fabric warehouse whose schema (tables, views, stored procedures) changes frequently. They want developers to author schema changes locally in Visual Studio Code using SQL, review those changes through pull requests before merging, and validate the resulting schema against a target before publishing. Which lifecycle management approach best satisfies these requirements?

Accepted Answer

Use a Fabric database project (SQL project) integrated with Git, allowing developers to author and build schema changes locally and publish validated changes to the warehouse.

Answer

Use a Fabric deployment pipeline with three stages and rely on the automatic schema comparison to author changes directly in the production stage.

Answer

Connect the workspace to Git and have developers edit warehouse tables directly in the Fabric portal, committing changes after each edit.

Answer

Export the warehouse as a Dataflow Gen2 and version the query definitions in an external repository.