BugZero found this defect 39 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/11/2024
SQL Server 2019 on Linux
SQL Server 2019 on Windows
build lower than 15.0.4365.2
15.0.4365.2
Fixes an issue in which the automatic seeding operation for a database remains in LIMIT_CONCURRENT_BACKUPS after adding the database to a new availability group or an existing one created with automatic seeding, even though this SQL Server instance doesn't have any other active seeding, virtual device interface (VDI), or backup threads.