"Leila" <Leilas@hotpop.com> wrote in message
news:eo9$H28aGHA.3524@TK2MSFTNGP04.phx.gbl...
> Thanks Paul,
> I used item 2 successfully in SQL2K. What about "Download Only Conflict
> Resolve" in SQL2K? It seems to work fine when you want the changes go only
> to subscriber, not vice versa. This resolver has not been documented
> anywhere. Hilary has promised to tell more about it!
>
>
>
> "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
> news:%23$VcCX8aGHA.4936@TK2MSFTNGP05.phx.gbl...
>> In merge replication the flow of data by default is bidirectional between
>> the publisher and subscriber, however this can be overridden if required.
>> In SQL Server 2005 there seems to be 3 independant ways this overriding
>> can be done:
>>
>> (1) SQL Server Upload Only Conflict Resolver. BOL: "Changes uploaded to
>> the Publisher are rejected; changes are downloaded to the Subscriber".
>> There is also the inverse conflict resolver for downloading only. (set at
>> design time for the publication)
>>
>> (2) the -EXCHANGETYPE parameter (can be set at run time for the
>> subscription)
>>
>> (3) @subscriber_upload_options (set at design time for the publication)
>>
>> Firstly, I've not used (1) but suggest according to the BOL definition
>> that that this is something of a misnomer as there can't be any conflicts
>> which get resolved - it's certainly not the place I'd first look to
>> control data flow. So, I suggest some sort of article is written to
>> clarify how these methods interact - when to use each one etc and
>> especially which overrides which when they are combined. It will probably
>> also be worthwhile explaining which is likely to be deprecated in the
>> future.
>>
>> Regards,
>>
>> Paul Ibison
>>
>>
>>
>>
>
>
>
>
>

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:%23$VcCX8aGHA.4936@TK2MSFTNGP05.phx.gbl...
> In merge replication the flow of data by default is bidirectional between
> the publisher and subscriber, however this can be overridden if required.
> In SQL Server 2005 there seems to be 3 independant ways this overriding
> can be done:
>
> (1) SQL Server Upload Only Conflict Resolver. BOL: "Changes uploaded to
> the Publisher are rejected; changes are downloaded to the Subscriber".
> There is also the inverse conflict resolver for downloading only. (set at
> design time for the publication)
>
> (2) the -EXCHANGETYPE parameter (can be set at run time for the
> subscription)
>
> (3) @subscriber_upload_options (set at design time for the publication)
>
> Firstly, I've not used (1) but suggest according to the BOL definition
> that that this is something of a misnomer as there can't be any conflicts
> which get resolved - it's certainly not the place I'd first look to
> control data flow. So, I suggest some sort of article is written to
> clarify how these methods interact - when to use each one etc and
> especially which overrides which when they are combined. It will probably
> also be worthwhile explaining which is likely to be deprecated in the
> future.
>
> Regards,
>
> Paul Ibison
>
>
>
>