Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
Hi, we are facing typical issue with Microsoft Fabric warehouse. We created a table and dropped (after deleting the data) but we still see the table in the schema (on the leftside under schema ancestor) and if we do a select command on that very specific table it was showing table or view doesnot exist. It is strange, is it something known issue, physically table deleted but on the user interface it is still visible (it causing very confusion). Is anyone face the same issue, please help us resolving the same.
Thanks.
Krishna.
Solved! Go to Solution.
Hi @ivamsikrishna,
This is a known UI behavior in Microsoft Fabric Warehouse. Even after a table is dropped, it may still show up in the schema explorer due to metadata caching in the UI. However, if you query the table and it returns "does not exist," then the table has been correctly dropped at the backend.
You can safely refresh the schema pane (right-click → Refresh) or reopen the warehouse tab to clear the UI cache. This doesn’t affect actual data operations and is just a temporary UI artifact.
Thanks,
Prashanth
Hi @ivamsikrishna,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @ivamsikrishna,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @ivamsikrishna ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@ivamsikrishna As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @ivamsikrishna,
This is a known UI behavior in Microsoft Fabric Warehouse. Even after a table is dropped, it may still show up in the schema explorer due to metadata caching in the UI. However, if you query the table and it returns "does not exist," then the table has been correctly dropped at the backend.
You can safely refresh the schema pane (right-click → Refresh) or reopen the warehouse tab to clear the UI cache. This doesn’t affect actual data operations and is just a temporary UI artifact.
Thanks,
Prashanth
| User | Count |
|---|---|
| 13 | |
| 6 | |
| 2 | |
| 2 | |
| 2 |