Database Throughput Unit – DTU

Bounding Box

Compute

Monitoring

% of current Performance Level Utilization Read Write CPU Memory

(coming)

Memory epresents the relative power (resources) assigned to the database Blended measure of CPU, memory, and read and write rates

C

Performance Levels (DTU) ASDB results Maximum DB size Price per day/month

(-50% during Preview)

Basic

1 3,467 tx/hour 2GB $0.16 / $4.995

Standard

S1: 5 S2: 25 S1: 283 tx/minute S2: 1,470 tx/minute 250GB S1: $1.30 / $40 S2: $6.45 / $200

Premium

P1: 100 P2: 200 P3: 800 P1: 98 tx/second P2: 192 tx/second P3: 730 tx/second 500GB P1: $30 / $930 P2: $60 / $1,860 P3: $240 / $7,440

Cust. #n Shard #n

SaaS Customer DB1 Customer DB2 Customer DB3 … Customer DB N

1.

2.

3.

Shard 1 1 Directory 2 Shard 2 3

Example Sharded Model

Business Continuity Problem

High availability platform

Single Logical Database DB S Ack Write P Write Ack S Reads are completed at the primary Writes are replicated to secondaries • • • Up to 4 synchronous replicas Transparent automatic failover Uptime SLA of 99.95%

Point In Time Restore

• • • Automatic Backup – Full backups once a week, diff backup once a day, log backups every 5 min – Daily backup files uploaded to geo-redundant Azure Storage Self-service restore – – REST API, PowerShell or Portal Creates a side-by-side database copy Tiered Retention Policy – – – Basic edition: last daily backup Standard edition: 7 days Premium edition: 30 days Restore as a new database sabcp01bl21 sabcp02bl21 sabcp03bl21 Copy backups to Azure Storage

LS XYZ

DB DB1

Active Geo-replication (Premium tier)

US West US East

LS ABC LS XYZ

Failover to secondary database • • • • • • RTO<1h, RPO<5m Automatic data replication and synchronization REST and PowerShell API to opt-in and failover DMV to guide failover decisions User controlled placement of up to 4 secondaries Creates secondary database with matching performance level

Design pattern #1

Active-passive compute with coupled failover • • • Optimized for co-located app and data tier Secondary is not used for app access Failover involves DNS change

Design pattern #2

Active-active compute with decoupled failover • • • Optimized isolated load balancing of the end user traffic Secondary is used for readonly access Failover does not involve DNS change

Design pattern #3

Active-passive compute with decoupled failover • • • Optimized for partial failures of the application stack Secondary is not used for application access Failover involve DNS change

BCDR Summary

no pre-allocated capacity) RTO<24h*, RPO<24h RTO<24h*, RPO<24h RTO<24h*, RPO<24h RTO<2h RPO<30m RTO<2h RPO<30m RTO<1h, RPO<5m * Target only, depends on the data size and scale of restores ** Not all disaster recovery features are available today

Scenario

Local failures Azure DB upgrades and maintenance Accidental data corruption Regional disaster DR Drill Online application upgrade Application failure Online application relocation Load balancing

Basic Tier

    

Standard Tier

     

Premium Tier

        

 

Basic: 1



5 DTU S1: 5



S2: 25



15 DTU 50 DTU

P1: 100 DTU (unchanged) P2: 200 DTU (unchanged) P3: 800 DTU (unchanged)

http://msdn.microsoft.com/en-us/library/jj585422.aspx

http://msdn.microsoft.com/en-us/library/azure/dn505719.aspx

http://msdn.microsoft.com/en-us/library/azure/dn741327.aspx

http://msdn.microsoft.com/library/azure/dn741339.aspx http://msdn.microsoft.com/en us/library/azure/jj650016.aspx

http://msdn.microsoft.com/en-us/library/dn720220.aspx

http://msdn.microsoft.com/en-us/library/dn720218.aspx

http://msdn.microsoft.com/en-us/library/azure/dn509565.aspx

, http://msdn.microsoft.com/en-us/library/azure/dn509563.aspx

http://channel9.msdn.com/Events/TechEd www.microsoft.com/learning http://microsoft.com/technet http://microsoft.com/msdn