Operational Defect Database
BugZero found this defect 67 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 2347023
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.
Last update date:
3/14/2024
Affected products:
SQL Server 2022 on Linux
SQL Server 2022 on Windows
Affected releases:
build lower than 16.0.4115.5
Fixed releases:
16.0.4115.5
Description:
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.
