How to share read only data

Hi,

I'm new to replication. Can anyone help with the following?

I want to publish the specific rows of data that are created on the publisher without accepting changes to those rows from subscribers, but do accept new rows (and changes to those rows) from subscribers.

EG. publisher creates rows 1 and 2 which are published to the subscriber

subscriber creates rows 3 and 4 which are merged back to the publisher

subscriber's updates (or delets) to rows 1 and 2 are not merged back to the publisher

So basically I want the publisher created rows to be published but remain as is whilst allowing subscriber created rows to be merged back to the publisher.

Hope is makes sense.

Thanks in advance,

Seedsy

Look at the properties of the articles (tables). There is an option called Synchronization Direction. That property, along with others, are what you are looking for.

By default, the Synchronization Direction property is set to Bidirectional, meaning, data will be synchronized both directions. I am pretty sure you can set this property to only allow synchronization one direction.

Hope this helps...

|||

I couldn't find any properties within the Publication's Articles' "Table Article Properties" but I found the SQLMergeObject's ExchangeType Property which allows upload / download / bidirectional. Shame its not a GUI option within the REPL tools.

Thanks I should be able to work it out from here.

|||Basically you want to publish ins/upd/del changes from the publisher to the subscriber, and only inserts at the subscriber to the publisher, correct? Seems like you want to implement bi-directional transactional replication (or possibly peer to peer replication), you can decide not to replicate upd and del commands at one of the nodes in the article properties.|||

Thanks Greg.

I can see that Table Article properties allows checking of the user permissions when merging subscriber changes for Insert, Update and Delete.

So is the approach that ... one should be using the restrictions of user permissions to disallow update and delete by the subscriber?

Seedsy

PS I should mention I'm using SQL2000 (V8.00.2039) SP4 so maybe I don't have all the bells and whistles.

|||i'm not sure it will work for merge replication, but I'm sure bi-directional transactional replication is what you need if you're on SQL 2000.