2

We have Transactional replication set up between a server 'A' and server 'B', where the Data from 'A' is getting replicated on the server B as database "B".

There is an issue reporting that one row in the subscriber database 'B' is missing. I re-tried the replication several times, still that one row is missing. Other than that, everything looks fine.

Anyone has an idea?

Kay
  • 23
  • 4
  • 3
    What do you mean by "re-tried the replication"?...have you tried generating a new snapshot for the distributor to work off of? – J.D. Jun 18 '21 at 22:17
  • @Kay, can you give an example of the table? I suppose this is not a large table, right; it's something with 10-20 rows, maybe? – Francesco Mantovani Jun 21 '21 at 07:29
  • @FrancescoMantovani after further investigation, i found the subscriber was paused syncing at some time in the past (say April 01), and then it re-started to sync (say June 01), and all data between those two times were not loaded into the subscriber. – Kay Jun 21 '21 at 17:48
  • @Kay, so is the problem solved now? – Francesco Mantovani Jun 21 '21 at 19:22
  • @FrancescoMantovani, not yet, would there be a way to sync the data during the period when the subscriber was paused? – Kay Jun 21 '21 at 19:53

1 Answers1

1

The solution will depend on two things.

  1. Size of the table, including the number of records
  2. Can you afford downtime to resync the full table

If it is a smaller table (generally speaking), you can use a data comparison tool (visual studio, Redgate SQL data compare or any other third-party tools) and sync the tables from source to target. If you have constraints, it might not work.

If you can afford downtime, you can drop this table (article) and add it back without a full snapshot of other articles in the same publication. See details here.

SqlWorldWide
  • 13,153
  • 3
  • 28
  • 52