Replace Fabric Lakehouse in place of SQL

[gauthami-tech]

Hi everyone,

We are currently exploring the possibility of migrating the SQL-based Leaf Application and Clinical database to Microsoft Fabric Lakehouse in order to improve performance and handle increasing data volume.

While reviewing the project, it appears that the Leaf database relies heavily on SQL Server–specific features, including a large number of stored procedures. For example, in the repository:

• src/db/build/LeafDB.Data.sql
• src/db/build/LeafDB.Exec.sql
• src/db/build/LeafDB.Init.sql

These scripts contain several SQL Server–specific components such as:

• Stored procedures
• Table-valued functions
• Temporary tables
• Dynamic SQL
• Other SQL Server–specific constructs

From our understanding, Fabric Lakehouse (and its SQL endpoint) currently supports:

• SELECT
• INSERT
• UPDATE
• Basic T-SQL queries

However, it does not fully support SQL Server stored procedures and some other advanced features that Leaf appears to rely on.

Has anyone attempted to run or migrate Leaf using Fabric Lakehouse instead of SQL Server?

If so, could you share your experience or guidance on the following:

1. Is this migration feasible with the current architecture?
2. Would significant modifications to the Leaf source code or database layer be required?
3. Are there recommended approaches or patterns for adapting Leaf to a Lakehouse-based architecture?

Any insights or suggestions would be greatly appreciated.

Thank you!