Forum Discussion
Relational database as a destination in Fabric
Why not just use a Warehouse table, Lakehouse table or even a csv or json in Lakehouse files?
Why can't you use a Delta Tables on the Lakehouse? They are ACID-compliant and relational. Just because they are capable of handling large datasets does not mean they are incapable of handling small datasets.
If you are just reading meta and configurations, you don't even need a relational database. You can just write that data to a file (XML, JSON, CSV, etc.) in a Lakehouse and read that file whenever you need it.
If it's smaller than 5mb, you could even store it in a variable in a data pipeline and retrieve it in real time when you need to refresh it.
Hi priyanfabriccom ,
Currently, none of Fabric is specifically designed for small relational database processes, and I have an alternative:
You can mirror an Azure SQL database in Microsoft Fabric to easily replicate the data that resides in the Azure SQL database directly into OneLake in the fabric in near real-time, without the need for a complex ETL process.
For more information on how to set up and use Azure SQL Database mirroring in the fabric, please see:
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi Yang,
Thank you for the response. But my concern is not the data ingestion from Azure SQL database or SQL database. Just to have small scale relational database to store simple configurations which are required for ETL automation. I can understand the use case of ASQL replication into OneLake.
Thanks
Priyan.