Forum Discussion
Advocate IVDoes Fabric Runtime 2.0 update affect Querying LH via Fabric Browser UI functions?
From what you describe, browser UI queries shouldn't be affected by the runtime change.
Queries through the SQL analytics endpoint (SQL query editor, Explore, Power BI on top) run on the SQL engine, not Spark, so the runtime version doesn't come into it.
The SparkCore usage on your Lakehouse items most likely comes from Spark background operations like:
- Someone previewing a table in the Lakehouse explorer
- Load to Tables from the explorer
- Table maintenance (OPTIMIZE / VACUUM) run from the UI or a pipeline
- Materialized lake views or shortcut transformations, if you use them
None of those need a notebook.
Runtime 2.0 matters for your own Spark items: notebooks, Spark job definitions, environments and libraries. Test those before switching an existing workspace. Also, the new Delta 4.x features are experimental, so don't enable them on tables the SQL endpoint or Power BI read.
Hope that clears it up.
Memorable MemberHi anon97242,
Fair point, my earlier steps only showed that Spark is involved, not who manages it. I am not aware of a Microsoft statement that settles whether the Lakehouse browser UI will keep working past the Runtime 1.x end-of-support date if the workspace runtime is never updated, so I would not rely on my reading of it.
The most reliable way to get a definitive answer is the Fabric runtime lifecycle documentation, and if it does not address the Lakehouse UI explicitly, a support ticket asking exactly your question (UI-initiated operations after the end-of-support date, no runtime change) will give you something citable. In the meantime, as noted by ShafiUllah-bc, queries through the SQL analytics endpoint run on the SQL engine rather than Spark, so those should not depend on the runtime setting.