Symptoms
A subscription isn't marked as deactivated after the distribution retention period for the subscription synchronization expires.
Resolution
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
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
