Forum Discussion
T-SQL SERVERPROPERTY(EngineEdition) does not return the value 12 for Lakehouse endpoint
Need to be able to dynamically determine if an end point is referring to Lakehouse.
A workspace includes a Lakehouse and a Warehouse.
When the statement select SERVERPROPERTY ('EngineEdition') is executed (i.e. from SMS), the value rerturned is 11 and not 12
as documented
https://learn.microsoft.com/en-us/sql/t-sql/functions/serverproperty-transact-sql?view=sql-server-ver17
11 = Azure Synapse serverless SQL pool or Microsoft Fabric
12 = Microsoft Fabric SQL analytics endpoint
Is this a known defect?
7 Replies
- V-yubandi-msftCommunity Support
Hi n_campbell,
Thanks for checking and sharing this suparnababu8 . I’ve tested on both Lakehouse and Warehouse SQL analytics endpoints in Microsoft Fabric, and I’m also consistently seeing.
SELECT SERVERPROPERTY('EngineEdition') AS EngineEdition;
-- Result: 11FYI:
Based on the documentation, we would expect EngineEdition = 12 for Lakehouse endpoints. Since both endpoints are currently returning 11, this appears to be either a documentation mismatch or a platform inconsistency.
For now, I’m treating this as a potential defect . In the meantime, please also consider submitting feedback through the official feedback form this will help the product team prioritize and address the issue.Link: Learn about Microsoft Fabric feedback - Microsoft Fabric | Microsoft Learn
Regards,
Yugandhar. - suparnababu8Super User
Hi n_campbell
I tried in both lakehouse and warehouse sql analytics end points. it is giving the result as 11. Seem like it's defect.
Let's wait for reply from CST team.
Thanks for bringing this into community.
Did I answer your question? Mark my post as a solution!
Proud to be a Super User! - V-yubandi-msftCommunity Support
Hi n_campbell ,
If you get a chance to go through my response, I hope it’s useful to you. In case you need anything more or if something’s not clear, just let me know.Thanks.
- n_campbellRegular Visitor
I had read it. Yes used the route in Fabric to add an item that way. Would like to see a reference (Defect) number that MS has created for this.
- V-yubandi-msftCommunity Support
Thanks for raising this it’s a valuable observation. At this time, Microsoft hasn’t published a public defect or incident ID for this specific issue. As community responders, we don’t have visibility into internal tracking numbers unless they’re officially surfaced in the Microsoft Fabric Known Issues.
Regards,
Yugandhar.
- V-yubandi-msftCommunity Support
Hi n_campbell ,
Could you let us know if your issue has been resolved or if you are still experiencing difficulties? Your feedback is valuable to the community and can help others facing similar problems. - V-yubandi-msftCommunity Support
Hi n_campbell ,
Has your issue been resolved, or are you still having any difficulties? If you need more information or help, please let us know.
Thanks