Fabric Materialized Lake Views Performance remediate
Diagnose and resolve performance issues with materialized lake views (MLVs) in Microsoft Fabric lakehouses. This skill covers refresh optimization, Spark job diagnostics, data quality constraint tuning, and lineage execution remediate.
When to Use This Skill
- MLV refresh runs are taking longer than expected
- Incremental refresh is falling back to full refresh unexpectedly
- MLV lineage execution shows Failed or Skipped nodes
- Spark jobs for MLV refresh are failing with errors
- "Delta table not found" errors during MLV creation or refresh
- Data quality constraints causing unexpected pipeline failures
- Need to enable or verify optimal refresh configuration
- Custom Spark environment tuning for MLV workloads
- Monitoring and interpreting MLV run history
Prerequisites
- Microsoft Fabric workspace with Lakehouse items
- Schema-enabled lakehouse (recommended for MLV support)
- Fabric notebook for executing Spark SQL commands
- Workspace Admin or Contributor role for scheduling and monitoring
- Access to Monitor Hub for viewing MLV run details
Quick Diagnostics Checklist
Run through these checks in order when remediate MLV performance:
| Step | Check | Action |
|---|---|---|
| 1 | Identify refresh mode | Verify optimal refresh toggle is enabled in lineage view |
| 2 | Check CDF status | Confirm delta.enableChangeDataFeed=true on ALL source tables |
| 3 | Review query patterns | Ensure only supported SQL constructs are used (see supported expressions) |
| 4 | Inspect run history | Open lineage view dropdown to see last 25 runs and their states |
| 5 | Check node failures | Click failed nodes in lineage to view error messages |
| 6 | Review Spark logs | Follow Detailed Logs link to Monitor Hub for Spark error logs |
| 7 | Validate data quality | Check if FAIL constraints are causing "delta table not found" errors |
| 8 | Assess source data | Determine if source has updates/deletes (forces full refresh) |
Step-by-Step Workflows
Workflow 1: Diagnose Slow Refresh
- Determine current refresh strategy - Navigate to Manage materialized lake views in the lakehouse ribbon. Check if Optimal refresh toggle is ON.
- Verify change data feed - Run the diagnostic script to check CDF status on all source tables. See scripts/check-cdf-status.sql.
- Check for unsupported expressions - Review the MLV definition for constructs that force full refresh. See Supported Expressions.
- Inspect source data patterns - If source tables have UPDATE or DELETE operations, Fabric always performs full refresh regardless of CDF status.
- Review partition strategy - Consider adding
PARTITIONED BYto large MLVs to improve refresh parallelism. - Attach custom environment - Configure a custom Spark environment with optimized compute for heavy workloads. See references/custom-environment-guide.md.
Workflow 2: Resolve Failed Refresh Runs
- Open lineage view - Navigate to Manage materialized lake views, select the failed run from the dropdown (last 25 runs available).
- Identify failed node - Click the failed node in the lineage graph. Review the error message in the right-side panel.
- Access Spark logs - Click the Detailed Logs link to navigate to Monitor Hub. Review Apache Spark error logs.
- Common failure patterns - See references/common-failure-patterns.md for resolution steps.
- Retry or recreate - For transient Spark failures, retry the run. For persistent errors, drop and recreate the MLV.
Workflow 3: Enable Optimal Refresh
- Enable CDF on all source tables:
ALTER TABLE bronze.customers SET TBLPROPERTIES (delta.enableChangeDataFeed = true);
ALTER TABLE bronze.orders SET TBLPROPERTIES (delta.enableChangeDataFeed = true);
- Verify CDF is enabled:
DESCRIBE DETAIL bronze.customers;
-- Check properties column for delta.enableChangeDataFeed=true
- Create MLV with CDF property:
CREATE OR REPLACE MATERIALIZED LAKE VIEW silver.customer_orders
TBLPROPERTIES (delta.enableChangeDataFeed=true)
AS
SELECT
c.customerID,
c.customerName,
c.region,
o.orderDate,
o.orderAmount
FROM bronze.customers c INNER JOIN bronze.orders o
ON c.customerID = o.customerID;
- Enable optimal refresh toggle - Navigate to Manage materialized lake views and verify the Optimal refresh toggle is ON (enabled by default).
Supported Expressions for Incremental Refresh
MLVs using only these constructs qualify for incremental refresh:
| SQL Construct | Notes |
|---|---|
SELECT | Only deterministic built-in functions. Non-deterministic and window functions force full refresh. |
FROM | Standard table references |
WHERE | Only deterministic built-in functions |
INNER JOIN | Supported for incremental |
WITH (CTE) | Common table expressions supported |
UNION ALL | Supported |
CONSTRAINT ... CHECK | Only deterministic built-in functions in constraint conditions |
Unsupported constructs that force full refresh:
LEFT JOIN,RIGHT JOIN,FULL OUTER JOIN- Window functions (
ROW_NUMBER,RANK,LAG,LEAD, etc.) - Non-deterministic functions (
current_timestamp(),rand(), etc.) - Subqueries in
SELECTorWHERE GROUP BYwithHAVINGDISTINCT- User-defined functions (UDFs)
Key Spark SQL Reference
List All MLVs
SHOW MATERIALIZED LAKE VIEWS IN silver;
View MLV Definition
SHOW CREATE MATERIALIZED LAKE VIEW silver.customer_orders;
Force Full Refresh
REFRESH MATERIALIZED LAKE VIEW silver.customer_orders FULL;
Drop and Recreate
DROP MATERIALIZED LAKE VIEW silver.customer_orders;
CREATE OR REPLACE MATERIALIZED LAKE VIEW silver.customer_orders
TBLPROPERTIES (delta.enableChangeDataFeed=true)
AS
SELECT ...;
Known Issues and Limitations
| Issue | Impact | Workaround |
|---|---|---|
| FAIL constraint + "delta table not found" | MLV creation or refresh fails | Recreate MLV using DROP action instead of FAIL |
| Schema names with ALL CAPS | MLV creation fails | Use lowercase or mixed-case schema names |
| Session-level Spark properties | Not applied during scheduled refresh | Set properties in custom environment instead |
| Delta time travel in MLV definition | Not supported | Remove VERSION AS OF or TIMESTAMP AS OF from queries |
| DML statements on MLVs |