April 15, 2009 at 8:34 am
Hi all,
Hope your well!
I'm having a play around replicating between 2 SQL instances (the publisher is running 2008 and the subscriber is running 2005), all going well, then I decided to see what happens when I deleted a record from the subscriber table. The record deleted fine, and when I try to validate the data the replication agent knows the record is missing but wont replicate anything over, is there anyway to automatically have the record replicate over again, despite it being missing?
oh, its transactional replication by the way.
Any help would be great.
Thanks
April 15, 2009 at 10:00 am
I believe you'll have to either reinitialize the snapshot or manually insert the missing record on the subscriber to get it going again.
April 15, 2009 at 10:04 am
Hi Brad,
Thanks for the reply, yeah, I re-initialized and it brought the record over. Was kind of hoping it would be clever enough to resolve the missing record its self, but hey, not to worry.
Thanks again,
April 15, 2009 at 10:21 am
I've seen this problem come up when I was dealing with sql 2000 transactional replication. For me, it didnt cause a problem until an update or delete needed to occur on the missing record. At that point the update/delete replication stored procedure on the subscriber would bark because the row wasnt there to update or delete. Hard to tell if that was your issue without actually seeing your error message. If this is the case, you can manually insert the missing row into the subscriber without reinitializing the snapshot.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply