4. Unified solution Easy to configure, manage, and monitor Reuse existing investments SAN/DAS environments Allow using HA hardware resources Fast seamless failover Detect failures reliably Able to stand multiple failures

5. Pre-existent Server failover Useful in consolidation scenarios Shared storage (SAN / SMB) Depends on storage redundancy Failover takes 30s to couple of minutes Server restart SQL instance is replica for one FCI Passive secondary nodes Failover Cluster Instances (for servers) New Multi-database Failover DBs that app depends on Direct attached storage Log synchronization Failover takes less than 30 seconds Secondary replicas are online SQL instance hosts replicas for one or more AG replicas Active Secondary Replicas Availability Groups (for groups of databases)

7. Multi-database Failover Multiple secondaries (4) Sync (max 2) / Async Compression & Encryption Manual/Automatic Failover Flexible Failover Policy Automatic Page Repair Seamless App Connectivity Configuration Wizard Monitoring Dashboard Diagnostics infrastructure System Center integration Full cross-feature support Contained Databases, FileStream, FileTable, Service Broker Active Secondaries Read workloads Backups PowerShell Automation Fast Failover Integrated Efficient

8. Sync Log Synchronization Async Log Synchronization

10. Pre-existent Server failover Useful in consolidation scenarios Shared storage (SAN / SMB) Depends on storage redundancy Failover takes minutes Server restart Multi-node instance Passive secondary nodes Availability Groups (for groups of databases) New Multi-database Failover DBs that app depends on Direct attached storage Log synchronization Failover takes seconds Secondary replicas are online Multiple Secondary Replicas Active Secondary Replicas Failover Cluster Instances (for servers) Increased Number of Secondaries Increased Availability of Readable Secondaries Add Azure Replica Wizard Support for Windows Cluster Shared Volumes E n h a n c e d D i a g n o s t i c s

23. Sync Log Synchronization Async Log Synchronization

25. “The increased readable secondaries availability means our users can still find answers online and the world keeps spinning” - StackOverflow

29. Sync Log Synchronization Async Log Synchronization

34. TitleComponent Show timestamps in XEL output in UTC (not adjusted to client SSMS computer)XEvents Viewer Warning about log synchronization behavior when primary replica is asyncDashboard System function IsPrimaryReplica(database_name)System function Add AG name (and replica name and DB name if relevant) to many more XEvents to allow better data correlation between the logs XEvents Report major HADRON Manager transitions to AlwaysOn XEvent sessionXEvents Add Replica name context to connection established error log entryError Log Dump relevant output from sys.dm_hadr_database_replica_states to SQL error log when replicas change to resolving state XEvents Add new error message to detect AG startup failure when quorum is forcedError Log Separate error msg 41142 (replica can't become primary) - raised for two importantly different reasons Error Log AlwaysOn Functions/DMVs should also support FCIs where applicableDMVs Improve the CREATE AG error message “AG already exists”, to say “It’s possible that a previous DROP AG operation, executed during cluster quorum loss, didn’t delete the AG from the cluster. If so, please retry the DROP operation” Error Message Remove FCI setup dependency on cluster.exe (deprecated) – Use PowershellError Log Show timestamps in XEL output in UTC (not adjusted to client SSMS computer) System function IsPrimaryReplica(database_name) Separate error msg 41142 (replica can't become primary) - raised for two importantly different reasons Dump relevant output from sys.dm_hadr_database_replica_states to SQL error log when replicas change to resolving state and 13 more..

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