Fabric Notebook: IntelliSense Fails for Tables in Schema-Enabled Lakehouse

[vapid128]

Hello Fabric Community,

I'm experiencing an issue with IntelliSense (table name completion) in a Fabric Notebook using Spark SQL (%%sql).

My setup involves connecting to what the documentation refers to as a "schema-enabled lakehouse". This means tables are organized under specific user-defined schemas (like dbo, upload etc.) within the Lakehouse's database structure, accessed via a 4-part path like WorkspaceName.LakehouseName.DatabaseName.SchemaName.TableName.

What works:

• Queries using the full 4-part path execute correctly.
• The USE WorkspaceName.LakehouseName.DatabaseName.SchemaName; command succeeds.
• After USE, queries using unqualified table names (e.g., SELECT * FROM MyTableName) work correctly within that schema.

The Problem: IntelliSense does not provide suggestions for table names (e.g., after typing FROM or SchemaName.). Basic IntelliSense for SQL keywords works fine.

Diagnostics:

• SHOW CATALOGS; only lists spark_catalog. The Lakehouse itself isn't listed as a catalog.
• SELECT current_schema(); returns an internal identifier string, not the logical schema name used in the USE command.
• Restarting the kernel doesn't resolve the issue.

This seems specific to this schema-enabled Lakehouse structure. Has anyone else encountered this IntelliSense failure specifically with schemas inside Lakehouses that aren't registered in SHOW CATALOGS? Is there a known limitation or workaround besides manually typing names?

Thanks!

[v-sathmakuri]

Hi @vapid128 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you!!

[v-sathmakuri]

Hi @vapid128 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-sathmakuri · Accepted solution]

Hi @vapid128 ,

Thank you for sharing your insights on the IntelliSense issue in Lakehouse. I completely agree when working outside the schema context, tables need to be manually referenced using the full path lke  Workspace.Lakehouse.Database.Schema.TableName.

I’d also recommend submitting your detailed feedback and suggestions through Microsoft’s official channels, such as the Microsoft Fabric Ideas.  to help bring attention to this limitation.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!