Timeline for Azure SQL database still incurring vcore charges despite move to DTU?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2020 at 7:54 | comment | added | lansalot | So, what happened today - I logged in, and those vcore charges had wiped back to the cost it was 3 days ago before I moved to DTU. Am guessing this was actually a billing error. Thanks for the input on the vcore model tho Sam, that was really helpful. | |
| Oct 8, 2020 at 11:55 | comment | added | Sam Cogan | The cheapest vCore price is $390 per month, these prices are not dynamic and apply so long as you have the DB running so it should be easy to calculate what you cost will be upfront. vCore specs are designed for workloads that need that amount of CPU and Memory, so if you don't need that then look at cheaper DTU model, that is what it is for. You can also look at the serverless option if you only want to pay per use. It's all relative, £33 a day is nothing for a demanding app that needs that level of performance. | |
| Oct 8, 2020 at 11:17 | comment | added | lansalot | Thanks Sam - I wondered if it was just that costs hadn't flown all the way through. Will monitor over the next day or two and see what happens, see if the vcore increases any. vCore costs seem astronomical tho - that was it practically on the lowest spec, and £33 in just a couple days isn't sustainable.. | |
| Oct 8, 2020 at 10:37 | history | answered | Sam Cogan | CC BY-SA 4.0 |