Missing replicated records

Hi gurus there,
I have a puzzling scenario here.
Environment: SQL Server 2K5 (sp2) EE + windows 2K3
I have a publisher server PubSrv_1and two subscriber severs SubSrv_1 and
SubSrv_2, there are two publications on the Publication_1, and
Publication_2, but they all contain the same table as article tbl_A
Publication_1 is a transational replication with Subscription on SubSrv_1
and Publication_2 is a transactional replication with updateable
subscription on SubSrv_2.
Issue: sometimes I find there are missing records which appear in tbl_A on
PubSrv_1 but not in tbl_A on SubSrv_2 while still in tbl_A on SubSrv_1. In
another word, some records in the publication table are NOT replicated to
one subscriber but still replicated to another subscriber.
I am confused how this happens. Could someone please shed some lights here?
TIA
Jeff
Can you check the conflicts log on the subscriber to see if the
missing rows are logged there?
On Jan 9, 3:03 am, "jeff_y" <jeffrey...@.abc.com> wrote:
> Hi gurus there,
> I have a puzzling scenario here.
> Environment: SQL Server 2K5 (sp2) EE + windows 2K3
> I have a publisher server PubSrv_1and two subscriber severs SubSrv_1 and
> SubSrv_2, there are two publications on the Publication_1, and
> Publication_2, but they all contain the same table as article tbl_A
> Publication_1 is a transational replication with Subscription on SubSrv_1
> and Publication_2 is a transactional replication with updateable
> subscription on SubSrv_2.
> Issue: sometimes I find there are missing records which appear in tbl_A on
> PubSrv_1 but not in tbl_A on SubSrv_2 while still in tbl_A on SubSrv_1. In
> another word, some records in the publication table are NOT replicated to
> one subscriber but still replicated to another subscriber.
> I am confused how this happens. Could someone please shed some lights here?
> TIA
> Jeff
|||Hi Hillary,
Thanks for your quick response.
I am not sure where the conflicts log are for the transactional replication.
More information:
I have even put a delete trigger on the problematic table at the subsriber
side to try to log any deletion on the table, but find the trigger has never
been fired off. So in another word, the missing records have never been
deleted as they were in fact never replicated over from the publisher side.
I find the two subscribers have different editions, the SubSrv_2, which has
seen the issues, has edition 3042, while SubSrv_1 has 3161. Do you think
this can cause the issue (I am not convinced though)?
Thanks,
Jeff
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:86aa0601-0caa-49ad-b9a1-d5d3cc732456@.f10g2000hsf.googlegroups.com...
> Can you check the conflicts log on the subscriber to see if the
> missing rows are logged there?
> On Jan 9, 3:03 am, "jeff_y" <jeffrey...@.abc.com> wrote:
>