• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 191
  • Last Modified:

SQL Merge Replication Problem

Hi All,

So I had a problem with my subscriber SQL server and had to restart the server.

Replication came back up fine afterwards and is working absolutely fine... HOWEVER...

I have checked a few count(*) on a number of tables and found there to be some rows missing at either end that were inserted around the time of the crash....

For example table tbl_asn has 402 rows at the Publisher but only 400 at the subscriber... and the time they were inserted was at the crash point.

My plan is to delete the records at the publisher manually and then recreate them again at the publisher.. given rep is working fine they should then replicate...?

Will this cause replication to fail when it tries to replicate the delete to the subscriber but not find a record??

SQL 2008 running on windows Server 2008.


1 Solution
Anthony PerkinsCommented:
If the snapshot for the Publisher is correct all you have to do is Reinitialize the Subscription.  If that is not the case than you can generate a new snapshot before Reinitializing all Subscriptions.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now