Flying High with Highly Available SQL Server Deployments
summary
Defines HA options for SQL Server with specifics: shared SAN, Block‑level mirroring, log shipping, Always On Availability Groups, and DataKeeper block-level replication that mirrors local disks between nodes and integrates with Failover Clustering Instances (FCI) so you can stay on standard edition licensing instead of Enterprise. Claims about costs: roughly a 70% cost saving versus moving to Enterprise with SAN. Gives concrete nines: 99% ≈ 3.65 days downtime/year, 99.9% ≈ 8.76 hours, high‑availability ≈ 52.5 minutes, continuous ≈ 5 minutes; cloud support includes EIPs/Route53.
AI-written summary · about
chapters (10)
- 0:00High availability intro
- 1:12Defining HA importance
- 4:04HA in aviation parallels
- 5:58Application-level high availability options
- 6:40Data-level HA solutions
- 8:03Understanding 'nines'
- 10:49Why HA matters for SQL
- 12:56HA options for SQL Server
- 14:40SOS DataKeeper intro
- 17:28Q&A
related talks
20mFlying High with Highly Available SQL Server Deployments- 20mFlying High with Highly Available SQL Server Deployments
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
20mChallenge to Triumph: Exploring Real-World High Availability in SQL Server Environments
42mHigh Availability with SQL Server on Linux- 20mChallenge to Triumph: Exploring Real-World High Availability in SQL Server Environments
52mHADR on SQL Server on Azure VMs: Everything you Need to Know