Direct Lake Fallback to DirectQuery: Find the Cause and Fix It
Report suddenly slow? Confirm whether Direct Lake really fell back, find the cause and fix it safely.
Watch the diagnosis: real English-language walkthroughs
Start with the fallback-specific video. Players open only when clicked; each also has an ordinary YouTube link for restrictive corporate browsers.

Decoding Direct Lake: The Truth Behind DirectQuery Fallback
Guy in a Cube / Patrick LeBlanc. Covers why a Direct Lake model switches to DirectQuery and what to look for when diagnosing it. Some UI details are older; use the November 2026 Microsoft steps below for current terminology.
Open the original video on YouTube
Chris Webb: Fabric Direct Lake Deep Dive
Explains architecture, monitoring and why Direct Lake may not behave as expected. Educational deep dive, not a verified fix for your specific workspace.
Watch on YouTube
Model not framed after creation or an XMLA change?
Demonstration linked by Fabric CAT’s Sandeep Pawar in his Direct Lake fallback analysis. Relevant to the missing-framing branch, not a universal fix.
Watch the linked demonstrationIf a thumbnail is blocked, use the video’s text link. Videos are third-party content and may show older interface versions.
Which Direct Lake problem do you have?
Advertisements
Confirm whether your model is Direct Lake on SQL or OneLake
Not every semantic model with a lakehouse source uses the same Direct Lake mode. Use the model’s actual connection/source expression and current model properties—not its name or a remembered creation wizard.
Uses a SQL analytics endpoint for table discovery and security checks. Can fall back to DirectQuery when permitted. Reads Delta data directly from OneLake when no fallback is needed.
Discovers/accesses Delta data through OneLake APIs. Does not use DirectQuery fallback. Failures require their own refresh, guardrail or security investigation.
Determine the actual mode of the affected table/model. A DirectQuery visual in a composite design is not automatically a Direct Lake fallback event.
- Open the semantic model’s supported web model view or an authorized metadata tool and inspect its source/connection expression. Microsoft documents the variant’s model expressions under Develop Direct Lake semantic models.
- Record the Fabric workspace, lakehouse/warehouse, semantic model, SKU and whether the report uses Direct Lake on SQL or Direct Lake on OneLake.
- Do not assume a model is SQL-based because its data source has a SQL analytics endpoint; both modes can use Fabric items exposing Delta tables.
How to tell if Direct Lake is really falling back
First inspect table-level status in the Direct Lake on SQL semantic model. In Fabric’s DAX query view or another approved DAX query client, run this exact query:
EVALUATE TABLETRAITS()Find the DirectLakeFallbackInfo column. Microsoft documents None as Direct Lake at the inspected table, while other values explain fallback eligibility/reasons. Record the affected tables and the time. The output is a diagnostic snapshot, not a guarantee about every later user query.
Then test the affected visual: open the report through Power BI Desktop, choose View → Performance analyzer → Start recording, refresh visuals and expand the slow visual. Microsoft illustrates a Direct query performance metric for a fallback query. If the metric isn’t present, investigate ordinary Direct Lake slowness too.
Need stronger evidence? Microsoft documents using SQL Server Profiler against the model’s Analysis Services XMLA endpoint and inspecting DirectQuery_Begin, DirectQuery_End and VertiPaq events. Merely seeing a SQL security/metadata probe does not prove the visual fell back. Keep traces private: they can expose query text or identifiers.
None for a native Delta fact table and View for a dimension SQL view tells you why a model might sometimes need SQL execution. Whether a specific measure uses DirectQuery depends on the query’s tables/relationships; don’t label the whole report as fully DirectQuery from one table alone. See a worked table-plus-view example from Fabric CAT.Authoritative instructions: Microsoft fallback detection and Performance Analyzer/Profiler walkthrough.
Advertisements
Table isn’t framed, or a recently added table is missing
Framing updates the semantic model’s reference to the Delta table snapshot. A newly created or programmatically modified table may be present in Lakehouse Explorer while the semantic model hasn’t successfully framed it.
- Check the table exists at the expected source, name and schema. Review recent renames, dropped tables, shortcut target changes and the model’s recorded source.
- Open the model’s refresh history, including its Direct Lake-related status. Refresh the semantic model through the supported UI or your established automation to request framing after the upstream write finishes.
- If you added tables with TOM/TMSL/XMLA, confirm the model was processed/refreshed as required before querying.
- Rerun
TABLETRAITS()and the originally failing visual. Verify expected row counts and freshness.
SQL views: decide whether SQL execution or a physical Delta table is appropriate
A nonmaterialized SQL view has no Delta files for Direct Lake to load as native columns. Direct Lake on SQL can query the view through DirectQuery when fallback is allowed; Direct Lake on OneLake cannot model that nonmaterialized SQL view as a native Direct Lake table.
- Inspect
DirectLakeFallbackInfoand confirm the affected table is a SQL view, not a physical Delta table. - Trace the slow measure’s referenced tables. A cross-table measure involving the view may force the query to use SQL even if other tables are native Delta.
- If SQL security and freshness requirements permit, materialize an equivalent, governed output as a Delta serving table using an approved Data Factory pipeline, notebook or supported materialization feature.
- Document its schedule and eventual consistency; compare the view and serving table for counts, types, null handling and RLS/OLS implications before redirecting the model.
- Alternatively, retain DirectQuery intentionally if the view must remain live or source-governed.
Real worked example: Microsoft’s Fabric CAT contributor Sandeep Pawar demonstrates a model containing an Orders Delta table and a Customer SQL view, including queries that can cause SQL fallback. Read the example and query observations. This is a documented demonstration, not a guaranteed repair in another tenant.
SQL endpoint RLS, DDM or OLS: preserve protections before optimizing
SQL endpoint row-level security (RLS), dynamic data masking (DDM) and object-level security (OLS) can require the SQL execution path. Power BI semantic-model security and source SQL security are different enforcement layers.
- Document the actual source SQL security rules and the effective identity used by the report/semantic model.
- Confirm whether
TABLETRAITS()points to a security condition and whether the affected query needs that SQL-protected table. - Consult the current Direct Lake security integration matrix for the model variant and the chosen identity mode.
- Where appropriate, assess an equivalent semantic-model RLS/OLS design—but only with governance sign-off and testing that each direct SQL/OneLake access path stays protected.
- If SQL source security is mandatory, accept the documented fallback or redesign the controlled serving layer rather than removing source rules.
Parquet files, row groups and row counts: check the actual Fabric SKU
Microsoft publishes separate limits for file count, row-group count, rows and model size. These are not interchangeable. A table can be below its row limit yet over its file-count limit due to frequent small writes.
| Capacity | Files / table | Row groups / table | Rows / table | Max model disk size |
|---|---|---|---|---|
| F2–F8 | 1,000 | 1,000 | 300 million | 10 GB |
| F16 | 1,000 | 1,000 | 300 million | 20 GB |
| F32 | 1,000 | 1,000 | 300 million | 40 GB |
| F64 / P1 | 5,000 | 5,000 | 1.5 billion | Unlimited* |
| F128 / P2 | 5,000 | 5,000 | 3 billion | Unlimited* |
Examples checked 22 November 2026 against the live Microsoft capacity table. *Other resource/working-set and capacity limits still apply. Verify your exact SKU and updated values before capacity decisions.
Which repair matches your exceeded limit?
Plan Delta table compaction for an eligible Lakehouse table; check the active snapshot and refresh/framing afterward.
Compaction does not reduce row count. Reduce model scope, build correctly aggregated serving tables or assess a higher capacity.
These have different evaluation semantics. Measure model footprint, working set, concurrency and paging before purchasing capacity.
Safe Lakehouse maintenance route: For a managed Delta table you are authorized to maintain, open Lakehouse → Tables → target table → Maintenance, then choose an appropriate OPTIMIZE operation. A Fabric Spark SQL alternative for a supported table is:
-- Run in an approved Fabric Spark SQL notebook.
-- Replace with your actual Lakehouse Delta table.
OPTIMIZE YourSchema.YourTable;That command changes physical file layout and uses compute. Confirm whether you control the table, whether the source is instead a managed Warehouse table, and whether special incremental-refresh or deletion-vector rules apply. Do not assume every Fabric item accepts the same Spark command.
After compaction, refresh/reframe the model and retest the same query and output. For automatic Lakehouse table care, see Microsoft’s cross-workload maintenance guidance.
Capacity memory pressure, query slowness and intermittent fallback
Memory limits and table guardrails are different. Microsoft’s Direct Lake overview explicitly says the maximum model memory figure is an upper paging limit, not the same kind of hard guardrail as file/row counts. Excessive paging can still make queries very slow.
- Capture the same affected visual in Performance Analyzer and use
TABLETRAITS()for its table conditions. - Review Fabric Capacity Metrics around the UTC time: competing jobs, query workloads, throttling, resource consumption and spikes.
- Check model dimensions/relationships, high-cardinality columns, DAX inefficiencies and cold-column loading. A slow Direct Lake visual may have no fallback at all.
- Compare controlled cold and warm tests, ideally with the same identity, source snapshot and concurrency. Avoid conclusions based on a single timing.
- If evidence indicates contention, reduce concurrent work, improve tables/queries and reassess capacity only after measuring the actual bottleneck.
DirectLakeBehavior: Automatic, DirectLakeOnly and DirectQueryOnly
These properties are for Direct Lake on SQL analytics endpoints. Changing them can turn a slow production report into a failing one. Use a nonproduction copy or a planned change window.
| Setting | What happens | When useful |
|---|---|---|
Automatic | Allows supported fallback when necessary. | Typical production availability-first setting. |
DirectLakeOnly | Returns an error rather than performing required DirectQuery fallback. | Controlled fail-fast testing; not a blind production fix. |
DirectQueryOnly | Executes through the SQL endpoint. | Controlled SQL-path performance comparison. |
In a supported model-editing experience, find Model → Properties → Direct Lake behavior. Record the original value and permissions before an edit; use supported TOM/TMSL/XMLA APIs only if you understand lifecycle and authoring compatibility. The nonexistent value DirectLakeOrEmpty is not an option.
What a DirectLakeOnly error tells you: an operation needs a path that DirectLakeOnly forbids. It does not automatically tell you that upgrading F32 to F64 is the right fix. Return to the precise reported cause and verify in a diagnostic copy.
Direct Lake on OneLake: there is no DirectQuery fallback
When this variant hits a table guardrail or framing issue, it cannot silently switch to the SQL endpoint for data. Microsoft documents model refresh failures for exceeded guardrails until the source is corrected. Other problems may involve item access, unsupported source features or memory/performance behavior.
- Open the semantic model’s Direct Lake refresh-history details and capture the specific error and UTC timestamp.
- Verify the Delta table path, metadata, schema and effective OneLake security/identity. OneLake shortcuts can also introduce access-path differences.
- Compare active table properties with the current SKU limits. Fix the actual overage, reframe and rerun the intended query.
- If the error is capacity throttling or model design rather than a guardrail, follow the evidence; changing a SQL fallback setting will not solve it.
Microsoft: OneLake variant and failure behavior · Related: OneLake shortcut 403 troubleshooting.
Real examples worth checking before making changes
1. SQL view mixed with a Delta fact table. Fabric CAT’s Sandeep Pawar walks through a sample semantic model, shows fallback reasons for its view, and explains that a measure crossing Delta and SQL-view relationships can execute using DirectQuery. Read the full experiment and see screenshots.
2. “How do I detect whether I’m really using DirectQuery?” A Microsoft Fabric Community discussion directs readers to EVALUATE TABLETRAITS() and explains the fallback information field. Useful for detecting the condition, but it is not proof that the questioner’s production performance issue was repaired. Read the community discussion.
3. Troubleshooting misleading model-outage symptoms. Another Community thread describes tables intermittently failing with missing-column or access messages. The posted discussion raises schema/metadata consistency and fallback as things to investigate, not a one-click confirmed solution. See the original reported symptoms.
Verify the original report is fixed—not just faster once
Repeat the exact failing action with the intended user and data. Use this completion checklist after making a minimal approved change.
Checklist state is local to this page session and is not submitted or stored.
Still failing? Copy this private support report
Direct Lake variant: SQL / OneLake / uncertain
Fabric SKU and model name (private channel):
UTC time, workspace/model IDs (private channel):
Affected visual or DAX query (sanitized):
TABLETRAITS / DirectLakeFallbackInfo values:
Performance Analyzer or trace evidence:
Current DirectLakeBehavior setting:
Source object: Delta table / SQL view / shortcut:
Delta file/row-group/row counts, if relevant:
Model refresh/framing results:
Security identity and source RLS/OLS notes (no secrets):
Change attempted, before/after results, rollback:Share only through your organization’s approved support channel. Do not post connection strings, tokens, protected row values or identifiable customer data publicly.
Frequently asked questions
Does every slow Direct Lake report mean it fell back to DirectQuery?
No. Cold transcoding, high-cardinality columns, model/DAX design, memory paging and capacity contention can also slow a Direct Lake visual. Confirm the model variant and query execution evidence before blaming fallback.
Can Direct Lake on OneLake fall back to DirectQuery?
No. Microsoft documents that it does not support DirectQuery fallback. Investigate refresh, model, source and capacity evidence instead.
What does EVALUATE TABLETRAITS() show?
In a Direct Lake on SQL model, the DirectLakeFallbackInfo field helps identify table-level fallback information. None indicates Direct Lake for that table at inspection time. Use Performance Analyzer or a supported trace to confirm a particular visual’s execution.
Will OPTIMIZE fix a Direct Lake row-count limit?
No. OPTIMIZE can compact small active Parquet files and lower file/row-group fragmentation. It does not reduce logical table rows. A row-limit issue needs source/model scope or capacity assessment.
Should I remove SQL RLS or masking to stop fallback?
Not as a generic fix. Source security and semantic-model security may protect different access routes. Keep existing protections until an approved alternative has been verified against permitted and denied identities.
Should I set DirectLakeOnly for every production model?
No. It converts a condition requiring fallback into a query failure. Use it only when your availability contract and change controls support fail-fast behavior; Microsoft’s documentation describes Automatic as the default production-friendly setting for the SQL variant.
Was this procedure tested against my Fabric tenant?
No. The guide uses Microsoft documentation and named demonstrations reviewed on 22 November 2026. The snippets were not executed on your semantic model and the instructions should be tested in an approved diagnostic environment first.
Microsoft documentation and evidence
Reviewed 22 November 2026. Source pages can change. Microsoft documentation takes precedence over independent examples or older videos.
- How Direct Lake works — fallback causes, TABLETRAITS, framing and settings
- Analyze Direct Lake query processing — Performance Analyzer and SQL Server Profiler
- Direct Lake overview — OneLake versus SQL and capacity guardrails
- Develop Direct Lake models — source expressions and supported modeling methods
- Direct Lake security integration — SQL, OneLake and model security
- Lakehouse table maintenance — OPTIMIZE and VACUUM safety
- Cross-workload Delta maintenance guidance
- Sandeep Pawar (Fabric CAT) — observed fallback behavior in a SQL-view example




