Today I was having a nice discussion with some colleagues about Fabric and pricing/licensing came up. I mentioned an F2 is only around €250 a month, but a colleague said “no no, it’s over €300”.
A bit confused, I pulled up the sizing table of my Fabric capacity in Azure, which looks like this:
Similarly, my colleague did the same for his capacity:
Weird right? Turns out I created a capacity in the region North Europe, while they created a capacity in West Europe. That’s almost 14% discount, just by selecting a different region! On an F2 capacity this doesn’t seem to be much, but on higher capacity this is quite a difference (e.g. around €1300 for an F64, which is over 15K per year).
Of course, a bit more thought should go into selecting a region than just the price of a Fabric capacity. Is the “cheaper” region acceptable towards latency and other SLAs? Are there already other Azure resources which are on another region? You definitely don’t want egress fees between the regions (depends on the Availability Zones). But for greenfield projects, it might be worth checking out the pricing differences between applicable regions.
It's time for T-SQL Tuesday again! And we're almost to number 200! T-SQL Tuesday is…
A while ago we suddenly had an error while trying to deploy one Fabric workspace…
I've uploaded the slides for my Techorama session Microsoft Fabric for Dummies and my DataGrillen…
I'm doing a small series on indexing basics for SQL Server, and on May 14th…
A short blog post about an issue with Fabric Mirroring (with Azure SQL DB as…
I'm starting a webinar series about SQL Server indexing with the fine folks of MSSQLTips.com.…