18756 Stone Oak Park Way, Suite200, San Antonio TX 78258 USA
100 Queen St W, Brampton, ON L6X 1A4, Canada
United States
share button
Free Webinar: Database Recovery Models And Its Significance : July 29, 2020. 

55246: SQL Always On High Availability with SQL 2016 Training


What 55246: SQL Always On High Availability with SQL 2016 training is all about?

The instructor-led course is created for Windows engineers and database admins to make them familiarize with Always on High Availability concepts. The Microtek Learning course uses SQL 2016 to explain the differences between SQL 2012 and SQL 2014.

  • START DATE
  • CLASS TIMINGS
  • DELIVERY MODE
  • PRICE
  • ACTION
  • 07/27/2020
  • 9:00 am - 5:00 pm EST
  • $ 1725
  • 09/02/2020
  • 9:00 am - 5:00 pm EST
  • $ 1725
  • 10/14/2020
  • 9:00 am - 5:00 pm EST
  • $ 1725
  • 11/16/2020
  • 9:00 am - 5:00 pm EST
  • $ 1725
  • 12/14/2020
  • 9:00 am - 5:00 pm EST
  • $ 1725
What are the course objectives for 55246: SQL Always On High Availability with SQL 2016 training?
  • Understanding Always-On and High Availability
  • Employing Failover Clustering for Server 2016
  • Deploying Failover Clusters on SQL
  • Working with Availability Groups
  • Performing maintenance
  • Monitoring and Troubleshooting Availability Groups
Who should attend 55246: SQL Always On High Availability with SQL 2016 training?

Professional Database admins, windows engineers and team leads are the suitable candidates for this course. Microtek Learning offers this lab intense course based on the experience of teaching over hundreds of batches to thousands of learners. Extremely hard efforts are made to keep the labs oriented to a concept like Transferring Logins or Adding Replicas. More emphasis is put on practical aspects as long exercises on theories are not effective. Experts deliver the course keeping the fact in mind that all the enrolled students are new to the tech and want to learn it.

What is the course outline for 55246: SQL Always On High Availability with SQL 2016 training?
  • 1. Introduction
  • 2. ALWAYSON AND HIGH AVAILABILITY CONCEPTS AND TERMINOLOGY
  • a). Concepts and Terminology
  • b). Table of Availability
  • c). High Availability
  • d). Causes of Downtime
  • e). Planned downtime
  • f). Unplanned downtime
  • g). Disaster Recovery
  • h). Recovery Time Objective (RTO)
  • i). Recovery Point Objective (RPO)
  • j). Recovery Level Objective (RLO)
  • k). Storage Area Networks (SAN)
  • l). Edition Changes from SQL 2012
  • m). SQL Server 2014 Changes
  • n). SQL Server 2016 Changes
  • o). Legacy Solutions prior to Always On
  • p). Failover Cluster Instances
  • q). Log Shipping
  • r). A Typical Log Shipping Configuration
  • s). Monitor Server
  • t). Replication
  • u). Database Mirroring
  • v). Database Mirroring Terminology
  • w). Principle
  • x). Mirror
  • y). Witness (red box in image above)
  • z). Database Snapshots
  • 3. WINDOWS SERVER 2016 FAILOVER CLUSTERING
  • a). Understanding Failover Clustering in Server 2016
  • b). Statefull High Availability Solution
  • c). Supported in both Standard and Datacenter
  • d). Servers should run similar hardware
  • e). Should run same edition
  • f). Hyper-V best with datacenter
  • g). Certified for Windows server logo
  • h). Shared Storage
  • i). Quorums
  • j). Node Majority
  • k). Node and Disk Majority configuration:
  • l). Node and File Share Majority
  • m). No Majority
  • n). Configuration
  • o). Cluster Networks Best Practices
  • p). Connection to nodes to shared storage
  • q). Private network for internal cluster
  • r). Public network for client connections
  • s). Cluster Aware Updating
  • t). Virtual Machine Failover Clustering
  • u). Preferred Owners
  • v). Failover Failback
  • w). Resources
  • x). Dependences
  • y). Heartbeat
  • z). Lab: Set up iSCSI Server
  • 4. SQL 2016 FAILOVER CLUSTER INSTANCES
  • a). Failover Cluster Instance
  • b). As A FCI Appears To A Client
  • c). Lab: Create A Configuration File By Running The Advanced Cluster Preparation Wizard
  • d). Lab: Complete The SQL Cluster Installation On SQL1
  • e). Lab: Install The Cluster On SQL2 And SQL3
  • f). Lab: Test the SQL Cluster
  • 5. SQL 2016 ALWAYS ON AVAILABILITY GROUPS
  • a). Availability Groups and Replicas
  • b). Primary Replica
  • c). Secondary Replicas
  • d). Availability Group Listener
  • e). Availability Mode
  • f). Synchronous Commit Mode
  • g). Asynchronous Commit Mode
  • h). Failover Modes
  • i). Automatic Failover Without Data Loss
  • j). Automatic Failover Requirements:
  • k). Manual
  • l). Manual Failover Requirements
  • m). Common Topologies
  • n). Lab: Create a SQL Instance For The Availability Group
  • o). Lab: Enable the SQL Server AlwaysOn Availability Group Feature
  • p). Lab: Set Up For Availability Groups
  • q). Lab: The Availability Group Wizard
  • r). Lab: SSMS and Availability Groups
  • 6. The Dasboard
  • a). The Dashboard
  • b). How to view logs
  • c). Using replication with Logins
  • d). Using partially contained databases
  • e). Lab: The Dashboard
  • f). Lab: Replicating Logins and Jobs
  • g). Lab: Contained or Partially Contained Databases
  • 7. Active Secondary Availability Group Actions
  • a). Reporting with Secondary Replicas
  • b). Configuring a Readable secondary
  • c). Read-Only Routing
  • d). Load Balancing
  • e). Lab: Configure a Read-Only Secondary
  • f). Database Backups with Secondary
  • g). Steps of Backup Using secondary
  • h). Backup Preference Options
  • i). Lab: Database Backup Using Secondary Replica
  • j). Lab: Configure a Read-Only secondary
  • 8. Maintenance
  • a). DBCC Checks
  • b). Database Adding and Removing
  • c). Lab: Add a Database
  • d). Lab: Remove a Database
  • e). Lab: Add a Replica
  • f). Lab: Remove a Replica
  • 9. MONITORING AND TROUBLESHOOTING AVAILABILITY GROUPS
  • a). The Dashboard in Depth
  • b). Events
  • c). Policy Based Managemnt for Availability Groups
  • d). Lab: Dashboard Wizards
  • e). Lab: Create an Extended Event Session
  • f). Lab: Using T-SQL
  • g). Lab: Policy based management for Availability Groups
  • h). Lab: Observe a Policy In Action
  • i). Lab: Create Three Conditions To Be Used In The RTO And RPO Policies
  • j). Lab: Create Two Policies RTO and RPO
  • k). Lab: Test The Policies
  • l). Lab: Change Endpoint Owner