Someone has delete by mistake a row of a table in the subscribed server/database.
I am getting the following error message:
The row was not found at the Subscriber when applying the replicated
(null) command for Table '(null)' with Primary Key(s): (null) (Source:
MSSQLServer, Error number: 20598)
Now I have restored the deleted row in the replicated server, but the distributor to the subscriber agent is taking so long to apply the changes (currently nearly 1.5 hours).
How can I make it do this update immediately?
Best Answer
If you have mistakenly removed a row on the subscriber that should receive an update through replication, the easiest way to fix would be to re-construct the missing row on the subscriber that matches the row that is failing to update.
Once the row is on the subscriber, the update can run successfully (even if it just writes the same value into the desired column), then replication should continue happily.
I have had this same scenario occur in the past and replication continued without issue.