Direct Lake vs Import vs DirectQuery in Power BI (2026)

· Power BI

Choose the right Power BI storage mode for finance and operations: compare refresh, performance, OneLake requirements, SQL fallback and migration trade-offs.

TL;DR

Choose Import when an ordinary refresh cycle meets the business need and the model fits your operating constraints. Evaluate DirectQuery when the source must answer queries directly. Consider Direct Lake when your curated data is already available as Delta tables in OneLake and avoiding a full Import copy is valuable.

Direct Lake does not eliminate modelling, data preparation or capacity planning. It changes how the semantic model reads data. This guide separates that architectural change from claims that it automatically makes every report faster or real-time.

Microsoft references were reviewed on 9 October 2026. Direct Lake has two forms with different behaviour; do not apply a limitation from one form to the other.

The three storage modes compared

DecisionImportDirectQueryDirect Lake
Data read pathCached model dataQueries sent to the sourceColumns loaded from OneLake Delta tables
Refresh meaningLoad data into the modelSource queried as users interact; caches still matterReframe references to Delta table files
Main dependencyRefresh pipeline and model memorySource query speed, concurrency and connectivityDelta preparation, model memory and Fabric capacity
Good starting caseMonthly finance reportingOperational data requiring source-side queriesLarge curated Fabric facts
Main trapStale data or expensive refreshSlow source queries multiplied by visualsAssuming no refresh work or memory pressure

Both Import and Direct Lake use the VertiPaq engine. DirectQuery delegates queries to the underlying source. Microsoft explains the distinction in its Direct Lake overview. Actual performance depends on the workload, not only the storage-mode label.

Import: still a sensible baseline

For a monthly management pack, a refresh after the finance close may be enough. Import offers predictable interactive analysis without asking the ERP to respond to every report interaction.

Start by removing unused columns, preserving transaction grain and designing a star schema. Consider incremental refresh where appropriate. A large source does not automatically require loading all history and every text field into the report model.

The decision changes when refresh windows become unacceptable, model size exceeds practical capacity constraints, or the business genuinely needs fresher data. Measure those constraints before migrating.

DirectQuery: source performance becomes report performance

DirectQuery can be appropriate when data should remain at the source or users need source-side query results without waiting for an Import refresh. It is not a promise of zero latency or an uncached result on every click.

A page with many visuals can generate many source queries. Filters, joins and measures translate into work for the underlying system. Poor source indexing, network delays and high concurrency can make an otherwise simple report slow.

Test with realistic users, slicers and dates. Check query folding, source workloads and any DAX or transformation limitations for the connector. Do not use DirectQuery merely because a table contains millions of rows.

Direct Lake: what actually happens

Direct Lake reads columns from Delta tables in OneLake into memory on demand. A model refresh updates references to the current Delta files, a process Microsoft calls framing. It does not import an entire replacement copy in the same way as Import. 1

That makes upstream preparation more important. Clean keys, currency conversion, historical dimensions and source deduplication need an owned transformation pipeline. Direct Lake does not turn an arbitrary Excel workbook or remote database into a curated Delta table.

The first query can need column loading; later queries may benefit from warm memory. Capacity pressure can evict cached data. Include cold and warm queries in the benchmark rather than quoting the fastest repeat run.

Direct Lake on OneLake versus Direct Lake on SQL

This distinction is essential for troubleshooting.

AspectDirect Lake on OneLakeDirect Lake on SQL analytics endpoints
Connection basisOneLake Delta tablesSupported SQL analytics endpoint
SQL endpoint couplingNot coupled to the endpointUses the endpoint architecture
DirectQuery fallbackNot supportedCan occur for applicable scenarios
Design questionOneLake access, supported objects and capacitySQL security, views and fallback behaviour

Microsoft documents that Direct Lake on OneLake does not support DirectQuery fallback. Direct Lake on SQL can fall back to DirectQuery, for example when SQL-based security is detected; applicable guardrails and model configuration also need review. 2

Do not write “Direct Lake always falls back when memory is full.” Column eviction and fallback are not interchangeable concepts, and the OneLake form has no fallback path.

Microsoft's development guidance also distinguishes composite modelling and supported creation paths. Features such as calculated objects referencing Direct Lake tables are identified as preview there; check the current feature matrix before depending on them in production.

Finance example: actuals and monthly budget

Suppose your organisation has detailed actuals in a Fabric lakehouse and a smaller monthly budget table. Before choosing a storage mode, define what one row means in each table.

Actuals might be transaction-level by posting date, account and business unit. Budget might be monthly by account and unit. Joining these facts directly can repeat budget values against every transaction. The error exists in Import, DirectQuery and Direct Lake alike.

Use shared dimensions to filter separate facts. Map the budget period consistently to the reporting calendar, then validate Actual, Budget and Variance measures at both monthly and annual totals. A lower-grain budget should not imply daily precision that does not exist.

If evaluating a composite model, confirm the supported combination for the Direct Lake form you use. Test filters across storage modes, credentials and query plans rather than assuming a small imported budget table is operationally free.

For the model foundation, use the Power BI modelling guide. For reporting definitions, see semantic models.

A benchmark that informs the decision

Use the same business questions and equivalent model logic for each candidate mode. Record:

  1. Freshness: time from source posting to availability in the report, including upstream ingestion and framing or refresh.
  2. Cold response: first opening of the report and first application of representative slicers.
  3. Warm response: repeated queries with cached columns or results.
  4. Concurrency: several realistic users, not only the author on an empty capacity.
  5. Refresh and source load: duration, failures and impact on other workloads.
  6. Capacity utilisation: memory, throttling and contention with other Fabric work.
  7. Correctness: totals, budget comparisons and restricted-user results.

For Direct Lake on SQL, also confirm whether the tested queries actually stayed in Direct Lake or used fallback. Otherwise you may be benchmarking SQL queries without realising it.

Set acceptable targets with stakeholders before testing. There is no universal row count or file size at which all teams should change storage mode.

Migration checklist

  • Curate Delta tables and define the pipeline owner.
  • Identify whether the proposed model uses OneLake or SQL-based Direct Lake.
  • Review supported data types, objects, capacity guardrails and preview dependencies.
  • Recreate explicit measures and model descriptions; storage mode does not define your KPIs.
  • Reconcile the new results with the existing finance pack.
  • Test actual access with the intended users and administrators.
  • Compare cold, warm and concurrent performance.
  • Keep a rollback route until the new model meets the agreed acceptance criteria.

If the source is still a collection of spreadsheets, follow the Excel-to-Power-BI migration guide before treating Fabric as the solution to an undefined reporting process.

Frequently asked questions

Is Direct Lake real-time?

Not automatically. Source ingestion, Delta table updates, framing and report behaviour all affect freshness. Measure end-to-end delay against the business requirement.

Does Direct Lake replace Import?

No. Import remains a useful option when refresh, memory and freshness requirements are satisfied. Direct Lake is especially relevant when curated data is already in OneLake.

Does every Direct Lake model fall back to DirectQuery?

No. Direct Lake on OneLake does not support fallback. Direct Lake on SQL can fall back in supported scenarios; inspect its configuration and query behaviour.

Will moving a slow report to Direct Lake fix it?

Not necessarily. Bad relationships, inappropriate grain and expensive DAX can remain slow or wrong in any storage mode. Diagnose before migrating.

Next step

Choose the simplest mode that meets your measured requirements, not the newest label. If you need an independent review of a finance model, discuss your Power BI reporting requirements. If AI exploration is part of the plan, read the Copilot readiness checklist next.