Udemy - Learn Microsoft SQL Server AlwaysOn HA Solution

What you'll learn:
Create 2 Node Windows Failover Cluster
Install SQL Server 2016 using GUI & Command Line
Configure Installed SQL Server Instance for AlwaysOn High Availability
Create and Configure Availability Grpoups
Add Database to Availability Group & Replica
Create and Configure AlwaysOn Availability Group Listener
Failover Availability Group (Automatic , Manual &Force)
Configure Backup on Availability Group & Replica
Monitor AlwaysOn Availability Groups State & Data Syncronization
Requirements
You should be aware of Microsoft SQL Server.
You should have a PC which support Virtualization Feature.
Description
Learn how to Setup,Configure and Monitor Microsoft SQL Server AlwaysOn feature.
Always On Availability Groups (SQL Server).
An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. An availability group supports a set of primary databases and one to eight sets of corresponding secondary databases. Secondary databases are not backups. Continue to back up your databases and their transaction logs on a regular basis.
Each set of availability database is hosted by an availability replica. Two types of availability replicas exist: a single primary replica. which hosts the primary databases, and one to eight secondary replicas, each of which hosts a set of secondary databases and serves as a potential failover targets for the availability group. An availability group fails over at the level of an availability replica. An availability replica provides redundancy only at the database level-for the set of databases in one availability group. Failovers are not caused by database issues such as a database becoming suspect due to a loss of a data file or corruption of a transaction log.
The primary replica makes the primary databases available for read-write connections from clients. Also, in a process known as data synchronization, which occurs at the database level. The primary replica sends transaction log records of each primary database to every secondary database. Every secondary replica caches the transaction log records (hardens the log) and then applies them to its corresponding secondary database. Data synchronization occurs between the primary database and each connected secondary database, independently of the other databases. Therefore, a secondary database can be suspended or fail without affecting other secondary databases, and a primary database can be suspended or fail without affecting other primary databases.
Optionally, you can configure one or more secondary replicas to support read-only access to secondary databases, and you can configure any secondary replica to permit backups on secondary databases.
Deploying Always On Availability Groups requires a Windows Server Failover Clustering (WSFC) cluster. Each availability replica of a given availability group must reside on a different node of the same WSFC cluster. The only exception is that while being migrated to another WSFC cluster, an availability group can temporarily straddle two clusters.
A WSFC resource group is created for every availability group that you create. The WSFC cluster monitors this resource group to evaluate the health of the primary replica. The quorum for Always On Availability Groups is based on all nodes in the WSFC cluster regardless of whether a given cluster node hosts any availability replicas. In contrast to database mirroring, there is no witness role in Always On Availability Groups.
Who this course is for
This course is targeted for student who have some level of understanding with Microsoft SQL Server (Any version)
SQL Server Database Administrator and Developers
Homepage
https://www.udemy.com/course/microsoft-sql-server-alwayson-ha-solution