Perfecting business continuity for Azure SQL DB
summary
Covers concrete configs and demos: uses a 2 vCore Gen5 Hyperscale DB, simulates 28,000 requests/min with JMeter, and triggers a SQL database failover command showing automatic H-replica promotion in about 10–20 seconds (demo ~14–15s) while Power BI/Grafana trace the blip. Recommends enabling Zone redundancy for 99.995% HA, using failover groups with customer-managed policy for DR, notes standby replica gives ~40% cost savings, and reminds that Geo-restore backups replicate hourly so RPO ≈ 1 hour.
AI-written summary · about
chapters (10)
- 0:00Business continuity intro
- 3:19Availability and SLA
- 8:37RPO and RTO explained
- 13:13Resiliency scope
- 18:55High availability architectures
- 24:09HA demo with zone redundancy
- 31:43Disaster recovery options
- 38:22Geo-redundant backups
- 40:52Key takeaways checklist
- 47:00Q&A
related talks
01h 01mAzure SQL Database-Business Continuity During Disaster
46mAzure SQL Database Business Continuity During Disaster
28mHA and DR at a glance with Azure Database for PostgreSQL
50mSQL Server to Azure SQL: Performance and Availability
54mDesigning Azure Data Disaster Recovery Strategies
43mLearn Azure SQL Database through Demos
52mMicrosoft SQL Server HA/DR on AWS
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask
