Operational Defect Database
BugZero found this defect 608 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 14810743
KB5018231 - FIX: Error 20598 after adding columns that have default constraints as part of the primary key for an existing table and configuring transactional replication - Microsoft Support
Last update date:
2/16/2023
Affected products:
SQL Server 2017 on Windows
SQL Server 2019 on Windows
Affected releases:
build lower than 14.0.3456.2
Fixed releases:
14.0.3456.2
Description:
Symptoms
Consider the following scenario: You create a table that has the primary key, and you add some rows to it in Microsoft SQL Server 2019 or 2017. You add a column that has a default constraint, and you modify the primary key to include the new column. You create a transactional publication and subscription for this table. In this scenario, the Distribution Agent fails when it tries to apply UPDATE or DELETE at the subscriber on rows that existed before adding the new column. Additionally, you receive the following "20598" error message: The row was not found at the Subscriber when applying the replicated UPDATE command for Table 'TableName' with Primary Key(s): (null)
Resolution
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 19 for SQL Server 2019 Cumulative Update 31 for SQL Server 2017 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.
