when suitable publisher with MSDTC. Single trigger updates one single one
> make your central subscriber the publisher and use immediate updating on
> the subscribers. Then make sure your polling interval is low. You should
> get the majority of your inserts happening in seconds.
>
> --
> 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 >
>
>
> "Maxi" <maxi_da@infovia.com.ar.sacame> wrote in message
> news:u8qGG1BMHHA.1240@TK2MSFTNGP03.phx.gbl...
>> Hi, i have SQL2k SP4.
>>
>> My replication topology is:
>>
>> 1 Subscriber central and 4 publisher (no conflic)
>>
>> ok, the subscriber is necesary update inmediate to publicher data, for
>> example:
>>
>> Pub A containt
>>
>> Empresa_id # Sucursal_id # monto
>> ------------ ------------ -------
>> 1 1 100
>> 2 1 200
>>
>> Pub B containt
>>
>> Empresa_id # Sucursal_id # monto
>> ------------ ------------ -------
>> 1 2 100
>> 2 2 200
>>
>>
>> Subscriber containt
>>
>> Empresa_id # Sucursal_id # monto
>> ------------ ------------ -------
>> 1 1 100
>> 2 1 200
>> 1 2 100
>> 2 2 200
>>
>>
>> The PK is Empresa_id + Sucursal_id
>>
>> ok.
>>
>> I need the suscriber update inmediate to publicher, for example:
>>
>> UPDATE TABLE SET MONTO=300 WHERE EMPRESA=2 AND SUCURSAL=2
>>
>> The update is necesary distributed transaction to PUB B only.
>>
>> UPDATE TABLE SET MONTO=300 WHERE EMPRESA=2 AND SUCURSAL=1
>>
>> The update is necesary distributed transaction to PUB A only.
>>
>> --------------------------------------------------------------------------------------------------------------------------
>>
>> ok, whats is major method to implement the scenario?
>>
>> Tks
>>
>>
>>
>> --
>>
>> Salu2
>>
>> -----------------------------------------
>> Microsoft MVP SQL Server
>> Culminis Speaker
>> ------------------------------------------
>>
>>
>
>
