Forum Discussion
Monitor Hub - Semantic Model
Hello,
I have couple of questions :
1- I saw many videos that when I create a lakehouse, there's by default a semantic model, but it's not created despite I have uploaded a file and loaded it into a table
2- In the monitor hub as I said I have loaded the file into a table but there's activity still running, I don't know why it's not succeed since I am able to view the table.
3- what's the metadata folder in the view files section in Table
4- what's the maximum size of onelake in F2 for example and the price of the storage and how I can know it ?
Thank you
Hi ahmedshalabyy12 ,
I’ll address the different questions separately:
- Default Semantic Model no longer auto-created This is not a bug — it's a deliberate Microsoft change. Since September 5, 2025, default semantic models are no longer automatically created when you create a warehouse, lakehouse, or mirrored item. To create one manually, open the lakehouse and select "New Power BI semantic model" from the ribbon, pick the tables you want, and confirm.
- Activity showing in Monitoring Center even though the table is visible This is expected behavior. When you upload a file and load it into a table, two separate processes run: the Delta table write to OneLake (fast, that's why you can already see the table) and the SQL Analytics Endpoint syncing its SQL metadata from the Delta logs (runs in the background and takes a few extra minutes). The activity you see in the Monitoring Center is that background sync — it will complete on its own, no action needed.
- The metadata folder in the file view of a table. You have two optiones. Right-click → Properties on a table shows high-level metadata in the UI: path, format, estimated row count, etc. Right-click → View files opens the actual underlying file structure in OneLake for that table.
- Maximum Lakehouse size on F2 and storage pricing There is no fixed storage limit tied to your SKU. The F2 (or any F SKU) defines your compute power in Capacity Units, not how much data you can store. Storage is completely decoupled and billed separately on a pay-as-you-go basis regardless of your SKU size.
- See Official pricing page: https://azure.microsoft.com/en-us/pricing/details/microsoft-fabric/
If my comments helped solve your question, it would be great if you could like the two comments and mark it as the accepted solution. It helps others with the same issue and also motivates me to keep contributing.
Thanks a lot, I really appreciate it.
AI was used to ensure clarity of wording
3 Replies
Hi ahmedshalabyy12 ,
I’ll address the different questions separately:
- Default Semantic Model no longer auto-created This is not a bug — it's a deliberate Microsoft change. Since September 5, 2025, default semantic models are no longer automatically created when you create a warehouse, lakehouse, or mirrored item. To create one manually, open the lakehouse and select "New Power BI semantic model" from the ribbon, pick the tables you want, and confirm.
- Activity showing in Monitoring Center even though the table is visible This is expected behavior. When you upload a file and load it into a table, two separate processes run: the Delta table write to OneLake (fast, that's why you can already see the table) and the SQL Analytics Endpoint syncing its SQL metadata from the Delta logs (runs in the background and takes a few extra minutes). The activity you see in the Monitoring Center is that background sync — it will complete on its own, no action needed.
- The metadata folder in the file view of a table. You have two optiones. Right-click → Properties on a table shows high-level metadata in the UI: path, format, estimated row count, etc. Right-click → View files opens the actual underlying file structure in OneLake for that table.
- Maximum Lakehouse size on F2 and storage pricing There is no fixed storage limit tied to your SKU. The F2 (or any F SKU) defines your compute power in Capacity Units, not how much data you can store. Storage is completely decoupled and billed separately on a pay-as-you-go basis regardless of your SKU size.
- See Official pricing page: https://azure.microsoft.com/en-us/pricing/details/microsoft-fabric/
If my comments helped solve your question, it would be great if you could like the two comments and mark it as the accepted solution. It helps others with the same issue and also motivates me to keep contributing.
Thanks a lot, I really appreciate it.
AI was used to ensure clarity of wording
Hi ahmedshalabyy12 ,
Thank you for reaching out to the Microsoft Fabric Community Forum, and thanks to the arabalca for sharing helpful insights.
Just checking in, were you able to resolve the issue using the suggestions provided? If not, please feel free to share an update, and we’ll be happy to assist further.
Your feedback will also help others facing similar challenges.
Thank you!Yes Thank you , arabalca solved it and I marked this topic as solved
