Does the selected DTU setting act as a cap on cost?
Yes. You are paying for the reserved compute, memory, and storage resources. You cannot exceed your selected DTU limit and the charges are based on the configured DTUs and storage.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I’m hoping to gain a clearer understanding of Azure SQL DB pricing framework, using the DTU model. For the avoidance of doubt, - yes I have read MS docs literature, however it still isn’t easy to grasp. My question: Using the below screenshot as a point of reference. When setting up a Azure SQL Db - while selecting the DTU & memory settings - Does the selected DTU setting act as a cap on cost? For example: if I were to set my required DTU maximum to 10 DTUs (labelled "A" in screenshot) and GB database size 250 GB (see "B" on screenshot) and the Azure port showed me an estimated monthly running cost of say $19.20 dollars (using $ just for illustration, see "C" on screenshot), does this act as a maximum running cost celling - of course excluding any changes to future DTU cost or taxes etc. I.e. the Azure cloud service limits compute and storage to set range (quantified as a DTU), so as long as my use of the DB is no more than the max DTU limit my DB cost can't exceed what is quoted? ![38768-dtu-as-max-cost-cap.png][1] [1]: /api/attachments/38768-dtu-as-max-cost-cap.png?platform=QnA
Does the selected DTU setting act as a cap on cost?
Yes. You are paying for the reserved compute, memory, and storage resources. You cannot exceed your selected DTU limit and the charges are based on the configured DTUs and storage.