Pull-quote: “Direct Lake is not faster DirectQuery. It is a different mode that eliminates a class of refreshes that should never have existed.”
Why this matters
Power BI has been deployed in three modes for a decade: Import, DirectQuery, and Composite. Each has trade-offs. Import is fast but stale; DirectQuery is fresh but slow; Composite is a compromise. Direct Lake — Power BI talking directly to Delta tables in Databricks SQL — is a fourth mode that eliminates a class of refresh problems that should never have existed.
The four modes
| Mode | Freshness | Performance | When to use |
|---|---|---|---|
| Import | Stale until next refresh | Fast | Small models, infrequent updates |
| DirectQuery | Live | Slow on large fact tables | Real-time-ish dashboards over modest volume |
| Composite | Mixed | Mixed | Hybrid scenarios |
| Direct Lake | Live (on Delta) | Fast | Lakehouse-native consumption |
Why Direct Lake works
Direct Lake reads Delta files directly into Power BI’s analytics engine without import. There is no refresh schedule. There is no DirectQuery overhead. The semantic model points at Unity Catalog tables and the engine handles the rest.
The conditions for it to work:
- Source data must be in Delta format
- Tables must be in Unity Catalog
- Model size must fit in the engine’s memory budget for the SKU
- DAX must be Direct Lake-compatible (most is; some isn’t)
Migration playbook
| Phase | Output |
|---|---|
| Discovery | Catalog of existing Power BI models · usage telemetry |
| Source landing in Delta | Sources moved to Delta tables in Unity Catalog |
| Semantic model rebuild | New model on Direct Lake |
| Visual rebuild | Reports and dashboards rebuilt against the new model |
| Parallel run | Old and new models in production simultaneously |
| Cutover | Old retired |
Governance benefits
- Row and column security live in the dynamic views in Unity Catalog, not in the semantic model. One source of truth for security.
- Lineage covers the entire path from source through Delta to Power BI.
- Performance tuning happens at the Delta layer (liquid clustering, OPTIMIZE, Z-order) and benefits every consumer, not just Power BI.
Closing
Direct Lake is the modern Power BI mode for Lakehouse-native consumption. The migration is methodical, the trade-offs are clear, and the result is faster, fresher dashboards with simpler operations.
