Join 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!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi,
Why do I have 2 different SQL Endpoint connection strings for different lakehouses located in the same workspace?
E.g lakehouse abc123 has the following SQL Endpoint connection string
- xxx-xxx.datawarehouse.fabric.microsoft.com
Lakehouse def456 has the following SQL Endpoint connection string
- xxx-xxx.datawarehouse.pbidedicated.windows.net
To retrieve the connection string, I click on the three dots (...) on the lakehouse and select View details.
@Barre ,
As per the documentation we will get SQL Endpoint for every Lakehouse which we create in a workspace.
https://learn.microsoft.com/en-us/fabric/data-warehouse/get-started-lakehouse-sql-analytics-endpoint
Hi @Arul , thank you for the response.
Yes, I´m aware that the SQL Endpoint connection string is the exact same for all lakehouses when stored in the same workspace. But my question is, why do some lakehouses, that are located in the same workspace in Fabric, have different naming in the SQL Endpoint connection string after datawarehouse.?
I have these 2 lakehouses in my workspace.
Lakehouse 1 has this SQL Endpoint - xxx-xxx.datawarehouse.fabric.microsoft.com
Lakehouse 2 has this SQL Endpoint - xxx-xxx.datawarehouse.pbidedicated.windows.net
Why do lakehouse 1 have FABRIC and lakehouse 2 have PBIDEDICATED?