DW Missing features compared to SQL server

[AJAJ]

Hi,

Currently so happy with SQL server. Its a high performing db system. its just flys. Im trying to move into lakehouse assuming it will be performing better and noticed many rich sql features are missing some basic ones too. 

1 - A simple identity column is missing. i know identity was recently added. However its only big int? bigint takes more space than other types. was it designed in a way so more compute is used? we use tinyint for dim.status and int for keys as needed. 

2 - im not able to see dependency of a table used by sp or view or notebook (even if it is parameterized within notebook)

i can query the dependencies as well in sql server.

3 - i know underlying table storage is actually delta file. however it would be good if such alter column data types are allowed.

4 - sometimes concurrent updates on a table throws error.

5 - is there any where i could find the list of features that are in SQL but not in DW? Just trying to find where DW is a much better system than Azure SQL server db.

yet to uncover more.

[v-tsaipranay]

Hi @AJAJ ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

Could you please let us know if the issue has been resolved? I wanted to check if you had the opportunity to review the information provided by @tayloramy and @apturlov   . If you still require support, please let us know, we are happy to assist you.

Thank you.

[tayloramy · Accepted solution]

Hi @AJAJ, 

Lakehouses and Warehouses do not support the full T-SQL language. If you want full SQL support like you're used to, I recommend using a SQL Database in Fabric (they just went into GA today). 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[apturlov]

Hi @AJAJ, thanks for your question. While it may make sense to compare SQL Server with Fabric Data Warehouse in certain scenarios, it is still an incorrect comparison. At the very high level, SQL Server is a transactional workload, while Fabric Warehouse is an analytical workload. They are designed and implemented to fulfil different purposes and achieve different goals. Therefore, there are functional differences between them. The correct comparison would be SQL Server vs Fabic SQL Database. Both are transactional workloads but the latter (Fabric Database) is fully integrated inside Fabric SaaS platfrom offering unique features not directly availabe with a aloud or stanalone SQL Server. Here is a link to learn more about how Fabric SQL database compares to a SQL Server database Limitations for SQL database - Microsoft Fabric | Microsoft Learn.

If you are interested in Analytical solutions in Microsoft Fabric, it offers two traditional analytical workloads: Lakehouse and Warehouse. They also have differences and you can learn about them here Microsoft Fabric Decision Guide: Choose between Warehouse and Lakehouse - Microsoft Fabric | Microso....

If, on the other hand, you need help with understanding all different kinds of stores that Microsoft Fabric offers, you can start here Fabric decision guide - choose a data store - Microsoft Fabric | Microsoft Learn.

Hope this information helps resolve your confusion.

If you find this answer useful, please give it kudos and/or accept it as a solution to your question.