Fabric Warehouse UI not syncing anymore

[Antongig]

1. New schemas, tables, and views don’t appear in Fabric UI
When I create a schema via SQL, e.g.

CREATE SCHEMA EISW; GO
the schema exists (you can see it in VS Code / query it in SQL).

But the Fabric UI (Warehouse Explorer) never shows it — even after days of refreshing.

This used to work about a month ago but doesn’t anymore.

2. Semantic models can’t see new objects either
Because the UI metadata doesn’t refresh, semantic models don’t recognize new schemas/tables/views.

Even though the objects are physically present in gold_warehouse and fully queryable.

That means you can’t import them into dashboards unless you work around it.

3. Behavior is inconsistent with the past
A few weeks/months ago, creating schemas/tables in SQL would eventually sync into the Fabric UI.

Now, it seems the metadata layer between SQL endpoint and Fabric UI/semantic models is no longer refreshing or is more restrictive.

[tayloramy · Accepted solution]

Hi @Antongig,

What you are seeing is almost always the SQL analytics endpoint metadata not refreshing, not the Warehouse "losing" objects. Here is the fastest way to force a sync and get both Explorer and the semantic model navigator to see your new schema and objects.

1. Force a schema scan in the Warehouse UI
   Open the Warehouse, switch to the "SQL analytics endpoint" page, and click the "Refresh" button in the Explorer toolbar. That triggers a metadata rescan for the endpoint. Docs: Refresh metadata in the Fabric portal. 
2. If the UI refresh does not pick it up, call the REST API
   Use the official "Refresh SQL endpoint metadata" API to resync the endpoint. It is GA and supports long-running operations. Docs: Items - Refresh SQL endpoint metadata. GA announcement: Fabric blog. 

   POST https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/sqlEndpoints/{sqlEndpointId}/refreshMetadata Authorization: Bearer <token> Content-Type: application/json 

3. Refresh the semantic model’s schema explicitly
   In the Service, open the model and use "Edit tables" > "Refresh schema" so the navigator re-reads the endpoint after the sync. Docs: Edit tables for Direct Lake semantic models. Community guidance: Refresh Schema tip. 
4. Sanity checks if it still looks stuck
   
   • Verify the objects via T-SQL:

     SELECT name FROM sys.schemas WHERE name = 'EISW'; SELECT s.name AS schema_name, t.name AS table_name FROM sys.tables t JOIN sys.schemas s ON s.schema_id = t.schema_id WHERE s.name = 'EISW'; 

   • If you need to verify from an external tool, copy the SQL connection string from the Warehouse "Settings > SQL endpoint" and test with ADS/SSMS or Desktop. Docs: Find and use the Warehouse connection string. 

Why this happens
The Explorer and the model navigator read from the SQL analytics endpoint’s metadata catalog. Automatic scans eventually pick up DDL, but under load or after idle periods it can lag. The manual UI refresh and the REST API are the supported ways to force a rescan on demand. Background on caching and endpoint refresh is covered here: Warehouse caching and the metadata refresh articles and discussions linked above. 

Optional automation
If you create schemas/tables in code or pipelines, drop a quick call to the refresh-metadata API right after your DDL, then run "Edit tables > Refresh schema" for your model as part of your deployment flow.

If you try the steps above and it still will not surface in Explorer after a successful API refresh, grab the item IDs and a recent correlation ID from the Network tab and open a Microsoft support ticket - there have been intermittent regressions, and Support can inspect the endpoint’s metadata job.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.