Improvement that sets distributed Always On Availability Groups to automatically seed to all replicas when you add a new database in SQL Server

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


This article describes an improvement when you use distributed Always On Availability Groups in Microsoft SQL Server. When you set automatic direct seeding, and you add a new database to the availability group, the database is automatically seeded to all replicas.

More information

This improvement is included in the following update for SQL Server:

Cumulative Update 10 for SQL Server 2016 Service Pack 1

To stop automatic seeding for an availability group after you apply this update, run the following script on the primary replica:

SQLALTER AVAILABILITY GROUP [availability_group_name]     MODIFY REPLICA ON 'secondary_node_name'       WITH (SEEDING_MODE = MANUAL)GO

This script cancels any replicas that are currently seeding and prevents SQL Server from automatically initializing any replicas in this availability group. It does not stop synchronization for any replicas that are already initialized.

For more information, see the "Enable automatic seeding on an existing availability group" section of "Automatically initialize Always On Availability group" on the Microsoft Docs website.


Learn about the terminology Microsoft uses to describe software updates.