strange replication

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

maxzsim - 27 Jan 2006 00:38 GMT

Hi ,

I have set up queued updating at local server. i have managed to create a
customer and it got replicated over to the other site.

However, when i tried to modify some details of the customer or even delete
that customer. and when i start sychronize it shows that x commands has been
delivered. But when i check at the other end , the customer record still has
not been updated/deleted.

Appreciate ur kind advise

tks & rdgs

Reply to this Message

Hilary Cotter - 27 Jan 2006 02:07 GMT

Did you check the conflict viewer - they could be logged there if there were
conflicts?

Signature

Hilary Cotter
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 - 12 lines]
>
> tks & rdgs

Reply to this Message

maxzsim - 27 Jan 2006 02:57 GMT

Hi ,

How/Where can i check if there's any conflicts ? i have setup as txn
replication but dun see any view conflicts during right-click.

I thought it's only for merged replication ?

tks & rdgs

>Did you check the conflict viewer - they could be logged there if there were
>conflicts?
[quoted text clipped - 4 lines]
>>
>> tks & rdgs

Reply to this Message

Michael Hotek - 27 Jan 2006 17:44 GMT

Conflicts can occur for either merge or transactional with queued updating.
In 2000, you have to right click on the publication to get to the conflict
viewer.

Signature

Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.

> Hi ,
>
[quoted text clipped - 14 lines]
>>>
>>> tks & rdgs

Reply to this Message

Pranil - 31 Jan 2006 03:31 GMT

Did you do a snapshot initialization for this set up ? I had the same problem
and found that some of the replication system tables are not created unless a
snapshot initialization is done from the publisher to the subscriber. You can
do a quick check by looking for sys.MSreplication_queue in the subscriber
database. There won't be an error anywhere (that I know of) which indicates
that the system tables are missing.

> Conflicts can occur for either merge or transactional with queued updating.
> In 2000, you have to right click on the publication to get to the conflict
[quoted text clipped - 18 lines]
> >>>
> >>> tks & rdgs

Reply to this Message