topic Re: Cannot Cross-workspace Spark SQL queries in Microsoft Fabric in Data Engineering

Cannot Cross-workspace Spark SQL queries in Microsoft Fabric

kurnivannoery — Tue, 24 Sep 2024 02:33:02 GMT

I encountered the error [REQUIRES_SINGLE_PART_NAMESPACE] while trying to perform cross-workspace Spark SQL queries in Microsoft Fabric. The error states that 'spark_catalog requires a single-part namespace,' but I received 'Workspace.Lakehouse.dbo.' Do you have any solutions?

Re: Cannot Cross-workspace Spark SQL queries in Microsoft Fabric

FabianSchut — Tue, 24 Sep 2024 06:04:55 GMT

Hi kurnivannoery,

Did you enable schemas in both lakehouses? This is necessary to achieve this result: "Make sure you join tables only from lakehouses that have schemas enabled. Joining tables from lakehouses that don’t have schemas enabled won’t work.".

What is the complete query you are using?

Re: Cannot Cross-workspace Spark SQL queries in Microsoft Fabric

kurnivannoery — Tue, 24 Sep 2024 06:14:38 GMT

this issue is solved by adding lakehouse in notebook, if you didn't add lakehouse you can query lakehouse data.

Re: Cannot Cross-workspace Spark SQL queries in Microsoft Fabric

Anonymous — Wed, 25 Sep 2024 06:06:50 GMT

Hi kurnivannoery

Glad that you have solved it! Do you mean choosing a default Lakehouse for your notebook? Can you share the final query statement that works? This would help people who may encounter similar errors.

Update:

I made a test. When selecting the lakehouse as the default lakehouse of the notebook, the query works without error.

Best Regards,
Jing

Community Support Team

Re: Cannot Cross-workspace Spark SQL queries in Microsoft Fabric

amitbhat05 — Wed, 06 May 2026 11:43:28 GMT

Hello

The idea is that when we are adding multiple lakehouses in the notebook, we should be able to query data from any lh without a dependency to pin it. I need to create a table in the pinned lh that needs to refer tables across muktiple other added lakehouses in the notebook, I should be able to add it? I am able to do in some cases where the pinned lh is the one I created myself and not in others where pinned lh is created by someone else even when I am admin across both workspaces. Is there some limitation like this in fabric?