1. Azure SQL Database for Business Critical Cloud Applications
Bill Gibson | Principal Program Manager
Sasha Nosov | Principal Program Manager
Jan Engelsberg | Program Manager
Charles Levine | Principal Program Manager
Karthika Raman | Senior Technical Marketing Manager

2. Meet Sasha Nosov
Principal Program Manager, Microsoft

3. Meet Karthika Raman Senior Technical Marketing Manager
6+ years at Microsoft, SQL Server Team
12 years of relational database experience

4. Course Topics
Azure SQL Database for Business Critical Cloud Applications
01 | Azure SQL Database Overview
02 | Business Continuity Solutions
03 | Using the Performance Model to Respond to Varied Throughput
04 | Understanding the Throughput Using Azure SQL Database Benchmark

5. Setting Expectations Target Audience
Developers/IT Pros developing or considering developing relational database applications in Azure
Suggested Prerequisites/Supporting Material
Understanding of Azure platform
Familiarity with Relational Database/SQL

6. Join the MVA Community! Microsoft Virtual Academy
Free online learning tailored for IT Pros and Developers
Over 1M registered users
Up-to-date, relevant training on variety of Microsoft products
“Earn while you learn!”
Get 50 MVA Points for this event!
Visit
Enter this code: AzrSqlDBNewTiers (expires 10/27/2014)

7. 02 | {Business Continuity Solutions}
Sasha Nosov| Principal Program Manager
Karthika Raman| Senior Technical Marketing Manager

8. Module Overview
Scenarios
BCDR Solutions
Application Design Patterns

9. Business Continuity Problem
Enabling the application to continuously operate during unplanned and planned disruptive events 2m

10. BCDR Tiered Model Basic tier Standard tier Premium tier
11/3/2019
Basic tier
Standard tier
Premium tier
Uptime SLA
99.99%
Predictable Performance B
S0, S1 or S2
P1, P2 or P3
Transactions per hour
Transactions per minute
Transactions per second
Database size limit
2GB
250GB
500GB
Point In Time Restore (“oops” recovery)
Any point <7 days
Any point <14 days
Any point <35 days
Geo-Restore (restore last daily backup to another region)
RTO<24h*, RPO<24h
Standard geo-replication (offline secondary, fixed DR pairing)
Not included
RTO<2h RPO<30m
Active geo-replication (up to 4 online secondaries, configurable regions)
RTO<1h, RPO<5m 1m
* Target only, actual time depends on the data size and scale of restores
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. Roles and responsibilities
Azure SQL Database
Customer (subscription owner)
Geo-distributed service
Customer metadata protection and recovery
Transparent high availability and data protection from local platform failures
Automatic geo-distributed backups
Automatic data synchronization of geo-replicated databases
Platform compliance testing and certification
Alerting impacted customers about their servers’ degradation during regional failures
Detecting user errors and initiating point in time restore
Planning, database prioritization and region selection for disaster recovery
Initiating geo-restore to the selected region
Initiating failover of the geo-replicated databases
Application DR drills

12. BCDR Scenarios in Service tiers
Basic
Standard
Premium
Local failures 
Azure DB service maintenance
Accidental data modifications
Regional disaster
DR Drill
Online application upgrade
Online application relocation
Load balancing

13. High availability platform
Critical capabilities:
Create new replica
Synchronize data
Stay consistent
Detect failures
Fail over
99.95% availability
Single Logical
Database DB P S
Write
Ack
Read
Value P S P S S
Reads are completed at the primary
Writes are replicated to secondaries

14. Restore as a new database from local backups
Point In Time Restore
11/3/2019
RA-GRS
sabcp01bl21
sabcp02bl21
Automatic Backup
Full backups weekly, diff backup daily, log backups every 5 min
Daily and weekly backups automatically uploaded to geo-redundant Azure Storage
Self-service restore
REST API, PowerShell or Portal
Creates a new database in the same logical server
Tiered Retention Policy
Basic - 7 days, Standard - 14 days, Premium days
sabcp03bl21
Copy backups to Azure Storage
LS XYZ DB
Backups
DB1
Backups
Restore as a new database from local backups
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. Geo-restore Self-service restore API Restores last daily backup
RA-GRS
RA-GRS
sabcp01bl21
US West
Storage geo-replication
sabcp02bl21
sabcp01bl21
sabcp03bl21
sabcp02bl21
sabcp03bl21
LS ABC
Restore to any server when needed
LS XYZ
Automatic copies of daily backups DB DB
US West
Self-service restore API
Restores last daily backup
No extra cost, no capacity guarantee
RTO>=24h, RPO=24h
Database URL will change after restore
US East

16. Standard geo-replication
US West
LS OPQ DB
LS ABC
LS XYZ
Geo-replication DB
North Central US DB
Failover and activation of secondary (during incident)
West US
RTO<2h, RPO<30m
REST and PowerShell API to opt-in and failover
Automatic data replication and synchronization
DMV+REST to monitor and guide failover decisions
Single offline secondary with matching performance level in the DR paired region
East US

17. Active Geo-replication
North Central US
LS DFE
Geo-replication
DB1
Failover and activation of secondary (any time)
Geo-replication
Geo-replication
LS XYZ
LS OPQ
Geo-replication
DB1.old
DB1
DB1
LS ABC
DB1
West US
East US
RTO<1h, RPO<5m
REST and PowerShell API to opt-in and failover
DMV+REST to monitor and guide failover decisions
Automatic data replication and synchronization
Up to 4 online secondary databases with matching performance level in any region
South Central US