Group the articles into different publications. The one which are download
only should be transactional, the others merge or queued updating. Queued
"Udit Ghai" <ghai.udit@gmail.com> wrote in message
news:1160713186.613705.304860@h48g2000cwc.googlegroups.com...
> thanks for the reply
> so the best option is that i make two publication one for the download
> only and the other for the updatable articles. another thing i wanted
> to ask was that what if i make a transactional replication for all the
> articles (including all of those that that need to be reflected back)
> and then for the tables that need updation back at the publisher i make
> a merge publication so that the updates can be reflected back. i want
> all the articles beacuse even if the merge session is not running, the
> data for those updatable tables can sent from the publisher to the
> subscriber instantaneously using the transactional replication.
> Which out of the two would be more effective as in performance and
> latency if
>
> 1. i have very few updates at the subscriber end
> 2. i have large number of updates
> and both of which need to be reflected back as soon as possible
>
> another question regarding the proxy is that if i use the queued update
> instead of MSDTC
> and make the queue reader countinous the proxy will not block the queue
> reader agent right? and what kind of performance hit am i looking at if
> i implement countinuous queue reader for updatable beacuse of the proxy
> thing
> thanks
>
> Hilary Cotter wrote:
>> I would remove these tables and make them part of a plain vanilla
>> transactional publication.
>>
>> If the firewall blocks the transaction it will hang on the subscriber,
>> and
>> then be rolled back in about 20 s.
>>
>> --
>> 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 >>
>>
>>
>> "Udit Ghai" <ghai.udit@gmail.com> wrote in message
>> news:1160656157.790632.100420@i42g2000cwa.googlegroups.com...
>> > hi all, my question is that i want to replicate some tables to another
>> > server using transactional publication with updatable subscribers. but
>> > i only want some of those published objects to be updatable like i'll
>> > send 3 tables of which only 1 of them should be reflected back to the
>> > publisher i.e is should be updataed at the subscriber.
>> > i know how we can do that in merge replicaiton but not in transactional
>> > replication.
>> > also i wanted to ask how does MSDTC work when there is a firewall. does
>> > it still allow immediate upload?
>> > thanks
>> >
>