Shulou(Shulou.com)06/01 Report--

After selecting the replication database server, we set the endpoint to ensure that port 5022 on the firewall is allowed

The AG listener is actually a virtual address. Through this address and IP, front-end applications can automatically detect this SQL high availability group and send requests and data to this address, similar to Exchange's NLB front-end address mail.contoso.com (but AG listener does not include Load Balancer functionality).

Next, it is up to the AG of the SQL server to automatically direct the data request to the 'current' primary database server. Why say 'current' primary database, because although we just set up the primary and standby SQL servers, but in operation, once the primary database is found to be disconnected, then the secondary database will immediately take over the service.

and becomes the primary role. So this is switched.

Here we set up a good listener DNS name and IP, port reservation 1433

Here I slightly describe this listener, before I thought that this virtual address of ag.contoso.com can be used as a universal SQL backend address, that is to say, all my front-end applications, when deployed, as long as they are required to fill in the backend database address, just fill in ag.contoso.com. This is wrong! Wrong! Wrong!

Although my SharePoint Server 2016 and Sky for Business Server 2015 use this ag virtual address directly in the database, this is not recommended by Microsoft! I also specifically consulted Microsoft for this problem, see https://partnersupport.microsoft.com/zh-hans/mpndataplat/forum/mpncatdb-mpnsqlsvr2016/sql-2016-always/4d73bb3c-4295-4c69-ad23-f0c70b7890b1 because this connection is a Partner forum, some children may not see, I screenshot for everyone to see.

Here's Microsoft's reply,

https://msdn.microsoft.com/zh-cn/library/hh313417.aspx

Anyway, to sum up, if other applications require to write databases in the future, it is better to write the FQDN of the main database honestly, and do not use AG to listen to the address.

Okay, let's move on.

Switch to the secondary database server and create a shared path to store some replication related data and logs

Go back to the main database AG configuration wizard and fill in the address above

Click Next to verify.

View configuration overview, click Done

Configuration Start

The configuration is complete and we can see that SQL Server 2016 Always On High Availability Groups have been created

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.