Problem in merge replication with one direction

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

umesh - 25 Feb 2006 16:51 GMT

Hi,

I have a database with SQL Server 2000 and many MSDE. I need to replicate
all MSDE database to the central Server, which is SQL Server 2000. Also I
dont need to replicate from central database to all other MSDE database. So
central database just acts as backup for all MSDE and also the replication
should occur in 5 seconds, as some client applications are connected to this
Server database to show the values in all MSDE database. I cannot do
Transactional replication since using MSDE as database in all machines excpet
the one used as Server.
Thus the topology is, Multiple publisher - Central Subscriber, with one
direction (ExchangeType=2 , publisher to subscriber only) and replication
interval as 5 seconds (PollingInterval 5).
Does this topology has any problem ?
The replication is working, but after some time, some tables dont replicate
and the conflict message comes like 'Cannot update as some process outside of
replication is accessing the row' .

Please comment on this...

Thanks in advance
Umesh

Reply to this Message

umesh - 26 Feb 2006 13:33 GMT

Hi

The actual error message is "The row was updated at 'publihser' but could
not be updated at 'subscriber'. Unable to synchronize the row because the row
was updated by a different process outside of replication."

Thanks in advance
Umesh

> Hi,
>
[quoted text clipped - 18 lines]
> Thanks in advance
> Umesh

Reply to this Message

Hilary Cotter - 26 Feb 2006 18:12 GMT

Did you disable any of the merge replication triggers?IIRC this will cause
this error.

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> Hi
>
[quoted text clipped - 34 lines]
>> Thanks in advance
>> Umesh

Reply to this Message

umesh - 27 Feb 2006 01:02 GMT

Hello Hilary

Thank you very much for the reply.

In my replication scenario, I am creating all the setup (database creation,
publications, subscription, everything) through scripts. After doing this,
the replication seems to work fine, by checking the values in both Publisher
and subscriber. But after some time, with out making any change in
replication settings, it seems that replication fails and the conflict viewer
shows the error message as I posted earlier.

Also in another dicussion I found the same problem mentioned by another
person and there it was asked to check whether any DTS action is going on. As
in our development enviornment some person might have tried for this or done
some thing related to DTS. Could you please tell me how can I check or
conclude that the replication problem is because of DTS. Or any other method ?

Thank you
Umesh

> Did you disable any of the merge replication triggers?IIRC this will cause
> this error.
[quoted text clipped - 37 lines]
> >> Thanks in advance
> >> Umesh

Reply to this Message

Hilary Cotter - 27 Feb 2006 16:31 GMT

It sounds like a row is present in the tables published for merge
replication which is missing replication tracking metadata. For an insert it
is easy to understand how this row could be present (non logged operations).
For an update it is more difficult to see how such tracking metadata could
be missing. Disabling replication triggers is one of the reasons which can
cause this. In your scenario I can't think of anything obvious.

Signature

> Hello Hilary
>
[quoted text clipped - 72 lines]
>> >> Thanks in advance
>> >> Umesh

Reply to this Message

umesh - 28 Feb 2006 10:35 GMT

Hello Hialry

Thank you very much for the reply.

Is this problem related with the replication topology ? Should I change the
replication topology to some other. What topology is better for this
requirement.

Currently, there are many MSDE database in different machines running every
time. Some client application need all the data together to show. For this, I
created all the MSDE as publisher and a central server database, which is
SQL-Server, as subscriber.
Used Merge replication (as MSDE cannot support Transactional) with one
direction (as one MSDE database does not want other MSDE data) and
replication interval as 5 seconds (as client application can show almost
current data). Also created push subscription in publisher (as to reduce the
load at subscriber).

Please comment on this.

Thank you
Umesh

> It sounds like a row is present in the tables published for merge
> replication which is missing replication tracking metadata. For an insert it
[quoted text clipped - 79 lines]
> >> >> Thanks in advance
> >> >> Umesh

Reply to this Message