Hide System views in Lakehouse/Warehouse

[Michal_Dubravci]

These 3 schemas shoud be placed in own folder so they don't mix with user defined schema

• INFORMATION_SCHEMA
• queryinsights
• sys

It looks ugly (various naming conventions), confusing and hard to read when there user defined schemas mixed with system schemas.
My suggestion to put it in "System" folder:

[v-prasare]

Hi @Michal_Dubravci,

We are following up once again regarding your query. Could you please confirm if the issue has been addressed through the feedback ideas you submitted or by upvoting an existing idea on the Microsoft Fabric Ideas portal? If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[v-prasare]

Hi @Michal_Dubravci , 

Thank you for your suggestion. The presence of INFORMATION_SCHEMA, queryinsights, and sys alongside user-defined schemas is by design. We understand your concern about readability and organization, and I’d encourage you to submit your detailed feedback and ideas via Microsoft's official feedback channels, such as the Microsoft Fabric Ideas.

Feedback submitted here is often reviewed by the product teams and can lead to meaningful improvement.

Thanks,

Prashanth Are

MS Fabric community support

[Michal_Dubravci]

Looking at my other Warehouse , it is really messy
 

[v-tejrama]

Hi @Michal_Dubravci ,

Yes, I completely agree with your suggestion. Right now, all the system schemas like INFORMATION_SCHEMA, queryinsights, and sys are shown together with user-created schemas like dbo, and it looks a bit confusing. It's hard to quickly understand which ones are system-generated and which ones we created.

If these system schemas are moved into a separate "System" folder, as you showed in your screenshot, it will look much cleaner and more organised. It will also help avoid mistakes and make it easier for new users to understand the structure.

Thank you,

Tejaswi.

[Poojara_D12]

Hi @Michal_Dubravci 

In the current interface, system schemas like INFORMATION_SCHEMA, queryinsights, and sys are displayed alongside user-defined schemas such as dbo under a common Schemas folder. This creates visual clutter, inconsistencies in naming conventions, and makes it harder to distinguish between user-managed and system-generated objects. As shown in the first screenshot, this mixed presentation can be both confusing and visually unappealing—especially in environments where multiple user-defined schemas are present.

A cleaner and more intuitive layout would be to separate these system schemas into their own dedicated "System" folder, as suggested in the second screenshot. This not only improves readability and navigation but also aligns with standard design principles seen in other platforms, where system components are logically grouped away from user content. Introducing a clear distinction—such as placing INFORMATION_SCHEMA, queryinsights, and sys under a System node—enhances user experience by making the UI more organized and reducing the chance of accidental interaction with system-level objects. This structural refinement would benefit both new users and experienced developers alike.