FIX: Automatic seeding fails when using an Always On availability group in SQL Server

Taikoma: SQL Server 2017 DeveloperSQL Server 2017 EnterpriseSQL Server 2017 Enterprise Core

Symptoms


Assume that you use an Always On availability group together with automatic seeding in SQL Server 2017. When you add a new database to the Always On availability group and set different default directories between the database and log, the automatic-seeding function fails.

Resolution


This fix is included in Cumulative Update 6 for SQL Server 2017.

Workaround


To work around this issue, do one of the following:

  • Use the same directory layout for every replica in the Always On availability group.
  • Configure the log default directory to the same location as the database default directory.
  • Use manual seeding.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Automatically initialize Always On Availability group

Learn about the standard terminology Microsoft uses to describe software updates.