Before this update, whenever you wanted to check a table, fix a broken pipeline, or run a fast SQL test, you had to open a full notebook or go to SQL endpoint. Both features are great, but opening one just to look at a few rows feels like additional efforts.
Microsoft finally fixed this by adding the Lakehouse Query Explorer. It is a light SQL editor right inside the Lakehouse screen, so you can run queries instantly without waiting switching to SQL End Point and wait for big notebook to load .
What is the Lakehouse Query Explorer?
It is a basic Spark SQL tool built directly into your Fabric Lakehouse. Instead of switching pages or opening new files, you can write and run SQL right next to your data tables.
It runs on the Lakehouse Livy Endpoint, which means your query session starts up very fast.
What You Can Do With It
- Run SQL Instantly: Click the New SparkSQL Query button, or right-click any table to start writing code immediately.
- Use Multiple Tabs: You can open several tabs at the same time to compare different tables or test two things at once.
- Query Across Different Lakehouses: You can join data from different folders, Lakehouses, or workspaces in one simple query without moving any files around:
SQL
SELECT *
FROM FinanceWorkspace.SalesLakehouse.sales.orders o
JOIN MarketingWorkspace.CustomerLakehouse.crm.customers c
ON o.CustomerID = c.CustomerID
- View and Export Results Quickly: Filter, sort, or search your query results right on the screen. You can also download the output as a CSV, JSON, or XML file, or make simple charts.
- Save as a Spark View: Once your SQL code works, you can save it as a View so your team members can find and use it easily.
Speed and Performance
The first query you run takes a few extra seconds to start up the session. But after that, every query runs right away because the system stays warm and ready in the background.
Things It Cannot Do Yet
This is a brand new feature, so keep these limits in mind:
- It only works with Spark SQL (no Python, PySpark, Scala, or R).
- It does not save your query history yet.
- Your queries will not auto-save if you close the tab.
- You cannot schedule queries to run automatically here (you still need Notebooks or Pipelines for that).
- No live co-working with team members in the same query tab.
Why This Help Us Every Day
It might look like a small design update, but it saves a lot of time every day.
You no longer have to build temporary notebooks just to do basic job checks like:
- Checking raw incoming data
- Troubleshooting pipeline errors
- Inspecting Delta table changes
- Doing quick spot-checks on new data
Final Thoughts
This update shows that Microsoft is listening to developers and trying to make Fabric less clunky to use. By cutting out extra clicks and long load times, we can focus more on actual data work.
If you are already on Fabric, give the Lakehouse Query Explorer a try.
If this helps, ✓ Mark as Kudos | Help Others
Super User