1. SYED SAJID WASIM
SQL SERVER ALWAYS ON
Step by Step

2. SYED SAJID WASIM Manager ADC, DHAKABANK Limited
Focused on database and development technologies
MCT, MCSE, MCTS on Data Platform
18 Years IT Industry Experience
Working with SQL Server since version 6.5

3. What is SQL Server AlwaysOn?
Introduced in SQL Server 2012
Requires SQL Server Standard/Enterprise Edition
SQL Server AlwaysOn describes two distinct SQL Server High Availability features:
AlwaysOn Availability Groups
AlwaysOn Failover Cluster Instance

4. Why SQL Server AlwaysOn?
Feature
Database Mirroring
AlwaysOn AG
Maximum number of secondary databases
1 Mirror
8 Secondaries
Requires Windows Clustering No
Yes, however the SQL Servers can be stand-alone
Automatic failover
Yes, requires witness server and high-safety mode
Yes, one
HA or DR
Choose one
Each secondary independently configurable
Groups of databases
No, each database is configured separately
Multiple databases can be grouped to failover together
Can be used for reporting
Only against a database snapshot of the  mirror
Yes
Offload backups
Connection to active database
Requires special connection string for failover
Redirection handled by Windows Clustering with a virtual name. Special connection string not required
Connection string to mirror or secondary database
N/A
Can be configured with an Application Intent connection string to automatically redirect or can use traditional connection string with server name.
Why SQL Server AlwaysOn?

5. FEATURES Grouping Databases into Failover Groups
Integration with Windows Server Failover Clustering (WSFC)
Uses WSFC quorum models
Uses Cluster Client Access Point
Important features
Database Health causing failovers
Support for Distributed Transaction Coordinator
Synchronous replicas
Optimized log transport
Load balancing

7. Business Intelligence
High Availability features for SQL Server 2016 Licenses:
Feature Name
Enterprise
Business Intelligence
Standard
Web
Express
Server Core support
Yes
Log Shipping
Database mirroring
Yes (Safety Full Only)
Witness only
Backup compression
Alwayson Failover Cluster Instances
Yes (Node support: Operating system maximum
Yes (Node support: 2)
AlwaysOn Availability Groups
Yes (up to 8 secondary replicas, including 2 synchronous secondary replicas) …

8. AlwaysOn Requirements
System Setup
Use Server Manager to install the Failover Clustering feature on all nodes.
Use the Failover Cluster Management tool to create a new Windows failover cluster.
Install a new standalone instance of SQL Server on each cluster node.

9. AlwaysOn Requirements
Database Setup
Availability groups must be created with user databases. Systems databases can't be used.
Databases must be read-write. Read-only databases aren't supported.
Databases must be multiuser databases.
Databases can't use the AUTO_CLOSE feature.
Databases must use the full recovery model, and there must be a full backup of them.
A given database can only be in a single availability group, and that database can't be configured to use database mirroring.

10. Steps Configuring AlwaysOn Availability Groups Install Windows Cluster
Install a Standalone SQL Server 2012
Use the domain account for the SQL service account
Open Port 1433 and 5022 or disable the Windows Firewall
Create a sample database
Set recovery model to Full
Back up this sample database
Enable the AlwaysOn feature on both instances using SQL Server Configuration Manager
Create an Availability Group using the Availability Group Wizard

11. DEMO

12. Resources Always On Overview
Understanding Quorum in a Failover Cluster
Understanding File Share Witness Placement
Configuring Availability Groups
What’s New in Failover Clustering in Windows Server 2012 R2

13. Q&A
SQL SERVER 2016
What’s Your Message?