Question

A data engineering team manages a Fabric Warehouse whose schema (tables, views, and stored procedures) changes frequently. They want each schema change to be reviewed via pull requests, tracked with commit history, and validated for build errors before it is applied to the production warehouse. Which lifecycle management approach should the team adopt?

Accepted Answer

Use a Fabric database project (SQL project) in source control so schema objects are defined declaratively, built, and reviewed via pull requests before deployment.

Answer

Enable Git integration on the workspace and rely solely on the automatic sync of warehouse items to capture ad-hoc schema changes.

Answer

Create a deployment pipeline and use deployment rules to rewrite table definitions between the test and production stages.

Answer

Export the warehouse schema to a Dataflow Gen2 query and schedule it to reapply the schema nightly.