SQL Server 2017 AlwaysOn AG automatic initialization (XVI)
Summary
Consider the use of automatic seed settings in our production environment:
Because SQL Server 2016 and 2017 behave differently in disk file path requirements, 2017 can deploy data files on different volumes on primary and secondary copies, so 2017 is more flexible and more suitable for our environment.
The initialization of remote and large databases has to be verified in the production environment.
Initialize the copy through automatic seed setting, which can be synchronized with the initialization of the business database (including log backup).
