Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
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?
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
User | Count |
---|---|
50 | |
27 | |
20 | |
20 | |
19 |
User | Count |
---|---|
52 | |
50 | |
25 | |
24 | |
22 |