- The default semantic model takes up unnecessary real estate in the Fabric workspace. If I don't want the default semantic model, I should be able to remove it.
- The default semantic model is confusing, because you cannot modify it through the default semantic model item, instead you need to look inside the SQL Analytics Endpoint to modify the default semantic model.
- The default semantic model doesn't support server timings and some other features in DAX studio. For this, you need to create a new custom semantic model.
- The default semantic model cannot be manually refreshed, so you cannot clear it's cache for performance testing. For this, you need to create a new custom semantic model.
Bottom line: the default semantic model is annoying and should be removed.
9 Comments
- fbcideas_migusrNew Member
Agreed ... this consumes un-necessary resources and is contributing to global warming. And that is a bad thing. Don't do bad things Microsoft! :)
- fbcideas_migusrNew Member
Thanks for posting this. I don't like the default semantic model either. We never use it. We create a new one every time from the lakehouse. I wish they would remove the L shape grouping with the default semantic model and SQL Analytics endpoint as well. It takes up too much real-estate and dirties up an otherwise beautiful organization of items. There are other ways to get to the SQL analytics endpoint. I say get rid of the L shape grouping and access the SQL analytics endpoint through the ... "more options". Or it isn't unreasonable to just access the SQL analytics endpoint using the toggle dropdown in the upper right corner of the lakehouse. Many of us are using SSMS anyway.
Or allow users to configure the L grouping option on or off. To us it is very annoying to have many lakehouses in a workspace and it take up this much space.
- Thomas_EvansNew Member
Thanks for posting! Microsoft, please get rid of this unnecessary use of resources.
- CWright2New Member
Microsoft, please get rid of this unnecessary use of resources
- AFraaijNew Member
Also using a notebook to create a Lakehouse based on import sempy.fabric as fabric
It creates default semantic models outside the normal structure of Lakehouse creation like
--- LakehouseName
----- SemanticModelName
Example:
--- Lakehouse1
---- Lakehouse1
When you now delete the Lakehouse also the default semantic model is deleted.
To somekind of reason the sempy.fabric.create_lakehouse does create the default Semanticmodel not in this structure and when deleting the Lakehouse the semanticmodel still exists.
Needing to delete the workspace to remove it.
No issue for development but can not be done in production workspaces.
With sempy.fabric it also was possible to end with multiple semanticmodels having the same name, seeing in my development workspace:
Lakehouse3
Lakehouse3
Lakehouse3
- fbcideas_migusrNew MemberStatus added:New
- ToddChitt
Super User
Totally agree. Plus the "SQL Analytic Endpoint" for every Warehouse and Lakehouse is exactly the same, so why do we need to have it listed multiple times under multiple Lakehouses? (Department of Redundancy Department) - 42cdxNew MemberTotally agree
Recent ideas
Power BI Dynamic Subscription Capacity Consumption and Recipient Processing
Issue: The concern is that the dynamic subscription workload can consume a significant amount of capacity when generating and distributing personalized report outputs. This creates a scalability conc...vivek1234410 hours agoMicrosoft EmployeeNew4Views0likes0CommentsSchedule pipeline as Service Principal
It would be beneficial to be able to specify an anonymous sp or user account while creating a schedule to run a pipeline directly in the Fabric GUI. This is currently only possible via the rest api a...Juriaan8091125512 hours agoNew MemberNew5Views0likes0CommentsImprove Databricks Native SQL Development Experience in Power BI
As organizations increasingly adopt Databricks as their primary data platform, Power BI remains a preferred tool for semantic modeling, visualization, executive reporting, and self-service analytics....Applsfan13 hours agoNew MemberNew5Views0likes0CommentsFabric Workspace Operator Role for Pipeline Monitoring and Rerun Operations
Many organizations have dedicated production support and operations teams responsible for monitoring Microsoft Fabric pipelines and responding to failures. Currently, the available workspace roles ar...cmukul00713 hours agoRegular VisitorNew67Views4likes1CommentPower BI Admin to Disable the New Ribbon Preview & Control Rep Toolbar Visibility at Tenant Level
Allow Power BI Administrators to Disable the New Ribbon Preview and Control Report Toolbar Visibility at Tenant Level It takes too much real estate and by default users with low maturity leaves it a...icassiem13 hours agoPost ProdigyNew34Views5likes1Comment