Loading...
Loading...
Assume that you use SQL Server 2017. When you try to initialize multiple databases in a SQL Server Always On availability group (AG) by using automatic seeding, you notice that seeding for some databases may fail, and need to retry on one or more secondary replicas.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update for SQL Server: Cumulative Update 19 for SQL Server 2017 About cumulative updates for SQL Server: Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: Latest cumulative update for SQL Server 2017 Note When you use the fix, the corresponding pacemaker package must be applied in order for SQL Server on Linux to work correctly.
To work around this issue, you can retry, use backup or use restore for initialization.
Learn about the terminology that Microsoft uses to describe software updates.
The included affected builds are considered potentially affected, based on their release chronology relative to the identified fix.
Click on a version to see all relevant bugs
Microsoft SQL Server Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.