OPERATIONAL DEFECT DATABASE
...
...
A subscription isn't marked as deactivated after the distribution retention period for the subscription synchronization expires.
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 17 for SQL Server 2019 Cumulative Update 29 for SQL Server 2017 Note After you apply this cumulative update, you have to enable trace flag 8235 at a global level of the distributors. Enabling trace flag 8235 might decrease the performance of the distribution cleanup job because the sp_MSsubscription_cleanup procedure will be called from the distribution cleanup job instead of the expired subscription cleanup job. You can use the following TSQL command to enable trace flag 8235 at the global level: DBCC TRACEON(8235,-1) About cumulative updates for SQL Server Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server: Latest cumulative update for SQL Server 2019 Latest cumulative update for SQL Server 2017
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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.
