Ship Your Lakehouse Like Code: Deploying MLVs with a SQL-Only Configuration Notebook If you’re building with Materialized Lake Views (MLVs), you’ve probably felt the tension: the definitions live in code, but the Lakehouse itself is an environment-specific artifact. That gap is where deployments get messy—schemas drift, tables don’t exist yet, and MLV refresh behavior looks “random” when it’s really just reacting to configuration. This post lays out a pattern that closes that gap cleanly: a lakehouse configuration notebook that you promote through your deployment pipeline and run in every environment to create schemas, tables, and MLVs idempotently—using SQL cells only. The key is that MLVs are treated as “definition-driven assets” that can be iterated in dev and re-stamped into test/prod with the same notebook.

Want your #MSFabric #MaterializedLakeView deployments to stop being “it worked in dev” stories? Treat your #Lakehouse like code: one SQL-only configuration notebook, promoted through your pipeline, idempotent in every environment—with CDF set intentionally in the final cell.