Forum Discussion
Why Creating semantic model based on DataLake on OneLake Layer still shows SQL endpoint?
Hi jaryszek ,
When you create a report in Power BI desktop and publish you will find a semantic model and a report that is the expected behaviour.
SQL analytic endpoint is automatically configured whenever we create a Lakehouse, Cosmos DB or SQL DB.
If your requirement is to have SQL analytic endpoint for your data, I suggest you get the required data into lakehouse.
Thank you.
Hi jaryszek ,
Thanks for reaching out to the Microsoft fabric community forum.
This is expected behavior. Even when you create a semantic model on top of a Lakehouse in OneLake, the lineage view will still show the SQL analytics endpoint. That’s because every Lakehouse automatically provides this endpoint as the relational interface for Power BI.
In Direct Lake mode, queries are served directly from the parquet files in OneLake (not through the SQL engine), but the SQL endpoint is still shown in lineage as the connection object.
Please go through the below documents which may help you to resolve the issue:
https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview
https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Community Support Team
Ok but the difference is that when I am creating new semantic model on OnaLake through power bi dekstop,
additional sql layer is not created...
Why fabric and desktop are different while creating a new semantic model on OneLake?
Best,
Jacek
Hi jaryszek ,
When you create a report in Power BI desktop and publish you will find a semantic model and a report that is the expected behaviour.
SQL analytic endpoint is automatically configured whenever we create a Lakehouse, Cosmos DB or SQL DB.
If your requirement is to have SQL analytic endpoint for your data, I suggest you get the required data into lakehouse.
Thank you.Hi jaryszek ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.
Best Regards,
Community Support Team