1. Mission Critical Confidence SQL 2012/2014 AlwaysOn
October 10, 2015
Mark Skiles
(BI) Solutions | Cloud Architect
Seven Verbs, Des Moines
Minneapolis – SQL Saturday

2. Beginning of Deck Thank you Sponsors! Event After Party
Please visit the sponsors during the vendor break from 2:45 – 3:15 and enter their end-of-day raffles
Event After Party
Dave and Buster’s in Southdale Center. 3rd floor by Macy’s starting at 6:15
Want More Free Training?
PassMN meets the 3rd Tuesday of every month.
10/10/2015
SQL 2012/2014 AlwaysOn

3. Seven Verbs
equipping customers... illuminating their data, focusing their decision making
Business Intelligence / Custom .NET development
Data-driven Market Development
Highlight mission, client focus, and emphasize catch-phrase
Come from and been to over the years – networking company supplying infrastructure as progressed, gone from “I” to massage, manipulate and interpret data.

4. Agenda Introduction SQL 2012/2014 Highlights
High Availability / Disaster Recovery (AlwaysOn)
Azure - AlwaysOn Availability Groups Demo
Questions / Answers ?

5. About Mark Skiles Contact: mark@sevenverbs.com / (515)720-6195
“From data to decisions, integrity works!”
Contact: / (515)
International IT consultant, 28 years
Business Intelligence | Cloud Architect
Ownership - start to finish, design/delivery – distributed delivery teams...
Proud papa – 6 children, 3 grandchildren, married 31 yrs
“practical” technology

6. Big Data !

8. PEACE OF MIND AT THE RIGHT PRICE
Mission Critical Confidence with (AlwaysOn)
PEACE OF MIND AT THE RIGHT PRICE

9. SQL Server 2012/2014 HA & DR Solutions
Multi-site Failover Cluster Instance (FCI) for HA & DR
Shared Storage solution
Instance Level HA
Instance Level DR
Doesn’t require database to be in FULL recovery model 2
Availability Group for HA & DR
Non-Shared Storage solution
(Group of) Database Level HA
(Group of) Database Level DR
DR replica can be Active Secondary
Requires database to be in FULL recovery model 3
Failover Cluster Instance for local HA & Availability Group for DR
Combined Shared Storage and Non-Shared Storage

10. AlwaysOn Availability Groups
AlwaysOn Availability Groups is a new feature that enhances and combines database mirroring and log shipping capabilities
Flexible
Multi-database failover
Multiple secondaries
Total of 4 secondaries
2 synchronous secondaries
1 automatic failover pair
Synchronous and asynchronous data movement
Built in compression and encryption
Auto-page repair
Automatic and manual failover (new design)
Flexible failover policy
Integrated
Application failover using virtual name
Configuration Wizard
Dashboard
System Center Integration
Rich diagnostic infrastructure
File-stream replication
Replication publisher failover
Active Secondary
Readable Secondary
Backup from Secondary
Improves primary server performance by offloading work to secondary
Monitoring and Troubleshooting enhanced
Automation using PowerShell
Efficient
Stuff in Orange is not new.

11. AlwaysOn Availability Group Architecture
TechReady 14
9/23/2018 1:04 AM
AlwaysOn Availability Group Architecture
Windows Server Failover Clustering
(WSFC)
Database
Active Log
Synchronization
Availability Group uses WSFC for
WSFC is a Common Microsoft Availability Platform
SQL Server AlwaysOn Failover Cluster Instances
SQL Server AlwaysOn Availability Group
Microsoft Hyper-V
Microsoft Exchange
Built-in WSFC workloads (e.g. file share, NLB, etc.) and third party workloads
Inter-node health detection
Failover coordination
Primary health detection
Distributed data store for settings and state
Distributed change notifications
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. SQL Clustering / Availability Groups
Speak to Powershell scripting – Azure subscription connection,

13. Starting Topology
Database Mirroring
Log Shipping

14. New Topology A

15. AlwaysOn Availability Group Listener
TechReady 14
9/23/2018 1:04 AM
AlwaysOn Availability Group Listener
Availability Groups Listener allow applications to failover seamlessly to any secondary; reconnecting through Virtual Network Name
ServerA
ServerB
ServerC
2 DB
2 DB
2 DB
TechAG1
TechListener1
Primary
Secondary
Primary
Secondary
Secondary
Application retry during failover
Connect to new primary once
failover is complete
and the listener is online
Parameter Sample: -server TechListener1;-catalog HRDB
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Considerations for Availability Groups
All SQL servers (including the secondary in the DR site) in the same Windows domain
One Windows Server Failover Cluster spreads over the primary and DR sites
All the databases must be in FULL recovery model
The unit of failover (for local HA, as well as DR) is at the AG level, i.e., group of databases – not the instance
Consider using Contained Database for containing logins for failover
For jobs and other objects outside the database, simple customization needed
No delayed apply on the secondary like log shipping
Removing log shipping means the regular log backup job is removed
Need to re-establish periodic log backup (essential for truncating the log)
AlwaysOn Dashboard
System Center Operations Manager
New Tools for Monitoring & Alerting

17. Failover Clustering Improvements

18. AlwaysOn Multi-site Failover Cluster Instance
TechReady13
9/23/2018
AlwaysOn Multi-site Failover Cluster Instance
HA & DR Solution
Provide High Availability at the Instance Level
Unit of failover = SQL server instance
Maintain same virtual network name after failover. Clients re-connect to same name
Instance restart requires database to go through recovery
Provide Disaster Recovery at the Instance Level
Provide Disaster Recovery protection from site failure: be it network, power, infrastructure or other site disasters.
Require storage based replication technology and networking considerations
Multi-subnet support:
Version
Native Support
Implementation
SQL Server 2008 R2 NO
Create stretch Virtual-LAN (VLAN) to act as a single subnet
SQL Server 2012
YES
IP address OR dependency support within SQL Server setup
SQL Engine skips binding to IP’s not online on start-up
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

19. Multi-subnet Clustering
Corpnet
Network Name: SqlClust OR
IP1:
IP2:
Node1
Node2
Node3
Node4
subnet 1
subnet 2
Enables Geographic clustering
Local Site
Remote Site
SAN Replication

20. TempDB on Local Disk WHY WE ENABLE THIS? BENEFITS IMPORTANT NOTE!
tempdb access occupies large % of SAN I/O
Fast local HDD/SSD becomes standard Server configuration
BENEFITS
Better overall performance
Cost saving
IMPORTANT NOTE!
Ensure that tempdb local paths are available to SQL Service on all the nodes
LOCAL TEMP DB (Fast disk, SSD)
LOCAL TEMP DB (Fast disk, SSD)
primary
Secondaries
Shared Disk (SAN)

21. SQL 2012 AlwaysOn Demo Availability Groups Windows Azure
SQL Server 2012 will help unlock new insights with pervasive data discovery across the organization while providing tools for IT to deliver credible, consistent data and large scale analytic and data warehouse solutions.

22. DEMO Agenda Show SQL 2014 AlwaysOn template – new portal
Demo existing working cluster/AG
Create Cluster (AIT-Cluster) - .76
Enable AlwaysOn (AIT-HADR-SQL1 & 2)
Create Availability Group
Note Backup/Restore – ‘No Recovery’
Restore MyDb2 onto SQL2
Demonstrate Manual Failover

23. Notable differences – Azure / on-prem
For AlwaysOn Availability Groups:
Availability group listeners are now available in Windows Azure. (only 1 listener per Cloud Service – uses its IP)
Also, you must work around a DHCP limitation in Windows Azure when creating Windows Server Failover Clustering (WSFC) clusters in Windows Azure. (will demonstrate) – static IP
For more information, see
Configuring Windows Failover Cluster in Windows Azure for AlwaysOn Availability Groups.

24. Basic Architecture
A virtual network containing multiple subnets, including a front-end and a back-end subnet
2 Domain controllers (Redundancy) with an Active Directory (AD) domain
Two SQL Server VMs deployed to the back-end subnet and joined to the AD domain
A 3-node windows cluster with the File Server Witness (FSW) quorum model
An availability group with two synchronous-commit replicas of 2 availability databases
Note: Chosen for simplicity not cost-effectiveness, example could use DC as quorum fileshare witness

25. Architecture Overview

26. Architecture Overview

27. Where we Begin Azure Network created/defined
Domain Controller – DNS, AD – DC1 & DC2
Azure Services – part of availability sets (same data center)
Storage service – all the vhd’s stored here…
Domain accounts for Installation and SQL Services
2. Cluster Nodes prepared – 5 VM’s
AIT-HADR-DC1 & DC2, SQL1, SQL2, FSW – File Server Witness
Installed the failover clustering feature
Added CORP\Install as member of local SQL1 & 2 administrator group
Add NT AUTHORITY\System as a login with following permissions: (DB)
Alter any availability group
Connect SQL
View Server State
Opened firewall for remote access of SQL Server
Network share $Backup created to backup/restore betw. servers
Speak to Powershell scripting – Azure subscription connection,

28. Azure portal – VM’s created

29. Azure portal – Virtual Network DNS Server(s)

30. Resources http://blogs.msdn.com/b/sqlalwayson/
(GUI)
(Powershell)
(James Serra)
versions of the Lab – scripted and UI – used combination of both
6. VM scripting – export, remove, import – will SAVE your subscription – used to start/stop, configure VM’s via Powershell
7. Windows Azure Powershell cmdlets
8. Windows Azure account (Trial) – connect Azure Powershell to subscription – defined in scripted version of tutorial
Speak to Powershell scripting – Azure subscription connection,

31. Remember to fill out your online evaluations for the event and any sessions you have attended. They will be online until 10/17/15.
Mark Skiles
(515)
10/10/2015