Enterprise Edition costs are absolutely skyrocketing for folks with >4 core CPUs. I’m curious about that too – especially in light of Microsoft’s approach to jacking up prices for on-premise SQL Server. Here’s the much harder query to write: we need to be ready when management asks, “So how much does it cost to host these databases on-premise, and do we have three replicated copies like SQL Azure?” SQL Server 2012’s AlwaysOn Availability Groups get us much closer to that solution, but it ain’t cheap. These aren’t unsolvable challenges – especially when the price is right, and today, it’s gotten a lot closer to right. That query also doesn’t warn you about features you’re using that aren’t available in SQL Azure, nor the security challenges of having your customer data offsite, nor does it cover how your applications might be impacted by a database that lives outside of your network, yadda yadda yadda. That’s how I like to do my projections, though – if I’m worried that the data will grow to a certain size, then I size the database for it, and that’s a reasonable projection number for my SQL Azure costs as well. My query lists the data file sizes – not the actual data sizes, so if you’ve comically overprovisioned your files with lots of empty space, you’ll get artificially high SQL Azure costs. For exact pricing, check the Azure pricing page and scroll down for SQL Azure, or use the Azure pricing calculator. Disclaimer: that query is probably wildly inaccurate because I write horrendous T-SQL and barely tested it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |