Forum Discussion
Fabric SQL Database vs Warehouse
Hi VaibhavTiwari ,
As my colleague mentioned tayloramy , I would also go with a SQL Database, mainly because this kind of metadata-driven framework behaves much more like an OLTP workload.
A Warehouse can work, and in fact I used one for similar application scenarios when SQL Database in Fabric was not GA yet. In the end, I migrated it to Database.
The main issue is that when you start having many repetitive processes, writes, status updates, logs, etc., the CU consumption in the Warehouse becomes noticeably higher. You can optimize queries and processes, but there comes a point where, with enough frequency and concurrency, capacity usage still increases because it is not the type of workload the Warehouse is primarily designed for.
For this use case, I would go directly with SQL Database.
If this helped, please consider giving it a Like. If it solved your issue, please mark it as the Accepted Solution to help others facing the same problem.
Thanks
Solution SageHi,
I've thought through this exact decision before, for metadata/logging specifically, SQL Database is generally the better fit, your metadata tables (pipeline configs, run logs, watermark tracking) are transactional in nature, frequent small inserts/updates, not big analytical scans, so OLTP characteristics matter more here than OLAP.
Warehouse is better suited for your actual data outputs/reporting layer, not for operational metadata like this.
If this helped, feel free to give it a kudos or mark it as solution, helps others find it too.