Flying High with Highly Available SQL Server Deployments
summary
Defines HA for SQL Server as surviving node and storage failures using clustering plus local disk replication instead of costly SAN, and shows a working setup using SIOS DataKeeper with block-level replication tied into Windows Failover Clustering and cloud IP routing. Gives concrete availability math: 99% = 3.65 days downtime, 99.9% = 8.76 hours, high-availability ≈ 52.5 minutes, with a claimed 70% cost saving versus moving to Enterprise licensing.
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
42mHigh Availability with SQL Server on Linux
20mChallenge to Triumph: Exploring Real-World High Availability in SQL Server Environments
52mMicrosoft SQL Server HA/DR on AWS- 20mChallenge to Triumph: Exploring Real-World High Availability in SQL Server Environments
47mPerfecting business continuity for Azure SQL DB
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask