Azure SQL Database – Service Tiers

Naturally the cost of Azure SQL Database directly relates to what tier and performance level you are using. Starting from the least expensive basic database to the more premium ones I thought it would be worthwhile capturing the costs (GBP) across all tiers.

Basic 5 DTUs

basic

Standard (S0) 10 DTUs

s0

Standard (S1) 20 DTUs

s1

Standard (S2) 50 DTUs

s2

Standard (S3) 100 DTUs

s3

Standard (S4) 200 DTUs

Same price? I don’t think they have this right?

s4

Standard (S6) 400 DTUs

s6

Standard (S7) 800 DTUs

s7

Standard (S9) 1600 DTUs

s9

Standard (S12) 3000 DTUs

s12

Premium (P1) 125 DTUs

p1

Premium (P2) 250 DTUs

p2

Premium (P4) 500 DTUs

p4

Premium (P6) 1000 DTUs

p6

Premium (P11) 1750 DTUs

p11

Premium (P15) 4000 DTUs

p15

Hopefully this paints a picture for you. I will have my say though. Basic tier database is something that you should NOT be using for production workloads, its quite obvious with the 2GB limit but worth reinforcing the point. Standard tier is more for your common workloads and premium is designed for high transactional volume where I/O performance is much more important to you – my hunch maybe they are utilizing SSDs? I am not sure but the premium costs are much higher.

There is another service tier called Premium RS (In preview). My understanding is that performance is similar to that of Premium HOWEVER only useful for workloads that can tolerate data loss up to 5-minutes due to service failures. I will probably not use this for production but then again it seems to be nearly half the cost of premium. Choices choices choices.

 

 

3 thoughts on “Azure SQL Database – Service Tiers

  1. Pingback: Dew Drop - November 25, 2017 (#2610) - Belated Black Friday Edition - Morning Dew

  2. Pingback: Azure SQL Database – Service Tiers - SSWUG.ORG

  3. Pingback: Forecast Cloudy – Create Microsoft SQL Azure DB via PowerShell | A posteriori

Leave a Reply