Azure SQL Database vs. Fabric Database
I'm curious to hear what others think, but in my opinion, creating a Fabric SQL Database is hard to justify unless you plan to maintain a substantial presence in Fabric with analytical workloads.
Why would I invest in Fabric capacity solely to set up a serverless database when I could achieve similar results with an Azure SQL Database, which costs less than $10 per month for light usage, especially in a development or QA environment, compared to a minimum of about $250 for a Fabric F2 capacity?
Additionally, in Azure, you can set up multiple free-tier Azure SQL Databases per subscription, each with resource limits, of course.
One could argue that with Fabric capacity, multiple databases can be created that share compute units (CUs), somewhat similar to an instance pool in concept.
And yes, I understand that a Fabric Database is essentially an Azure SQL Database under the covers.
Maybe there’s something I'm missing regarding the advantages beyond it already being mirrored in Fabric, and I would welcome feedback to change my mind.
