Hello Everybody,

Thanks to all of you that have answered my basic questions, I really
appreciated. I have some doubts related to the updating subscriber
scenario.

* When we talk about updating subscribers, we are talking about
transactional publications ONLY ???

* If I implement a transactional publication with the option of updating
subscribers, that mean that I can update any record pulled or pushed from
the Publisher server, but I can not insert new records?????
Am I correct????


Thank you very much in advance.

Marlene A. Roman

Thank you for your answer Paul.

Sorry, I'm still not sure if I should use Merge or Transactional in one
specific table:

Here is the situation: This is a Warehouse Management System, and we are
implementing the system at a second site at this moment.
I have a table PickDet table that have the details(records) for a pick
process of some items that I what to transfer from Site1 to Site 2
Site1 insert the records and when the products gets to Site2, these records
will be updated. This looks to me as a Transactional Publication with
updating subscribers,
but at the same time, I will have Transfers coming from Site 2 to Site 1, so
I will have records inserted in Site2 that need to be updated in Site 1, so
I think that I have a merge situation here, because both sites need to
insert records in the same table and update the others sites records.

I think I need a merge publication with updating subscribers, If something
like this exists.

In your answer you said that updating subcribers can be use in Snapshot and
Transactional, but I am not sure if you meant for MERGE PUBLICATIONS IS THE
DEFAULT???

If so I need to use MERGE. Am I correct???

Thank you very much in advance.


Marlene A Roman








[quoted text, click to view]

Marlene,
answers inline:

"When we talk about updating subscribers, we are talking about
transactional publications ONLY ???"

Not really - snapshot and transactional can both be implemented as updatable
subscribers, although it's not the default. For merge bidirectional changes
is the default, so each replication type can potentially have updating
subscribers.

"If I implement a transactional publication with the option of updating
subscribers, that mean that I can update any record pulled or pushed from
the Publisher server, but I can not insert new records?????"

No - inserts, updates and deletes are all possible.

HTH,
Paul Ibison

Marlene,
merge or transactional with updating subscribers would be suitable. Both
methods enable changes in both directions. If you need autonomy ie the
ability of the subscriber to be disconnected and still change records, then
merge would be more suitable (although queued updating subscribers is
another alternative). So, in your case if there is a constant connection,
then I'd use transactional with updating subscribers. The subscriber changes
enter a distributed transaction with the publisher so there's no posibility
of any conflicts arising.
HTH,
Paul Ibison