Unexpected Appearance of Warehouse in Microsoft Fabric Notebook

[Ve3]

Hello All 

I'm reaching out to get some clarity on a change we've noticed in our Microsoft Fabric environment, specifically within our notebooks. In short it is reagarding the addition of Warehouse to the Explorer tab of the notebooks.

This warehouses part did not exist previously in our explorer tab

Set up previously already had warehouse

Scenario:

Previously, in the Explorer tab of my notebook, I could clearly see everything organised as expected under Lakehouse, with both Tables and Files folders visible and accessible. My scripts worked fine with this setup, and everything was structured as it should be.

However, I recently noticed that a Warehouse has now appeared as an additional item in the notebook. We already have a warehouse set up in our environment, labelled with country names (e.g., UK), but this new warehouse display seems different. When I add the warehouse back into the setup, I am seeing new schemas, security folders, and other configurations that were not present before.

When I explore this new warehouse, I can see the Tables inside the dbo schema, but the rest of the fields (such as Views, Functions, Stored Procedures, etc.) seem to be mostly empty or not populated as expected.

To provide some context, I've attached a screenshot of an older version of the setup (please ignore the different structure as we have since made changes). The older image shows that the warehouse was not previously visible in the notebook.

Old Set Up 

Workspace: MIET
│
└── Lakehouses (aka UK, US, countries etc)
├── Files
│ ├── Raw Data (e.g., CSV, JSON, Parquet)
└── Tables
└── Data Tables

New Setup

Workspace: MIET
│
└── Lakehouses (aka UK, US, countries etc)
├── Files
│ ├── Raw Data (e.g., CSV, JSON, Parquet)
└── Tables
├── Structured Data Tables
└── Organised for Analysis

Warehouse
│
├── Schemas
│ ├── dbo (Default Schema)
│ ├── guest
│ ├── INFORMATION_SCHEMA
│ ├── queryinsights
│ └── sys
│ ├── Views
│ ├── Functions
│ └── Stored Procedures
│
└── Security
├── DB roles (Built-in)
└── DB roles (Custom)

Additionally, we’re seeing an error message stating: "This data source is not fully supported under the current global language."

Questions:

1. Can anyone explain why the Warehouse has suddenly appeared alongside the Lakehouse in the notebook? Is this a deliberate update or change in the environment?
2. What steps should we take to address the error message about the data source not being fully supported under the current global language?
3. Is the appearance of these new schemas and security folders in the warehouse expected behaviour, or does it indicate a configuration update?
4. Should the presence of the warehouse be ignored if it does not affect the current script

I've attached several screenshots to illustrate the changes and the error message we’re encountering, in the hope that they provide a clearer picture of what we’re seeing on our end.

Any insights or guidance on these questions would be greatly appreciated! Thanks in advance!

Added warehouse to test and these appearError messages

[NandanHegde · Accepted solution]

Recently tsql integration functionality has come within notebook for which you need to mount the fabric warehouse, hence you are able to see warehouse option

[v-nuoc-msft]

Hi @Ve3 

1.

Can anyone explain why the Warehouse has suddenly appeared alongside the Lakehouse in the notebook? Is this a deliberate update or change in the environment?

The addition of the Warehouse section is likely part of a recent update to Microsoft Fabric. This change aims to enhance data management capabilities by integrating data warehousing features directly into the notebook environment. It allows for better organization and access to structured data, which can be beneficial for analytics and reporting.

2.

What steps should we take to address the error message about the data source not being fully supported under the current global language?

The error message stating, “This data source is not fully supported under the current global language,” suggests that there may be compatibility issues with the language settings in your environment. Here are a few steps you can take:

Ensure that the global language settings in your Fabric environment match the language used in your data sources.

If the settings are correct, consider updating your environment or reconfiguring the data source connections to ensure compatibility.

3.

Is the appearance of these new schemas and security folders in the warehouse expected behaviour, or does it indicate a configuration update?

The appearance of new schemas and security folders in the Warehouse is expected behavior following the integration of the Warehouse feature. This structure allows for better data governance and security management.

4.

Should the presence of the warehouse be ignored if it does not affect the current script

If the Warehouse does not currently affect your scripts or workflows, you can choose to ignore it for now.

Regards,

Nono Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.