HOW TO IMPLEMENT UPDATE INMEDIATE WITH ONE SUBSCRIBER AND MULTIPLE PUBLISHER

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
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
>
|||Hi, my central subscriber is make inmmediate update!
But it has but publisher (4) and it is needed that subscriber it updates
when suitable publisher with MSDTC. Single trigger updates one single one
and I need that depending on the filter she updates to publicher X
Salu2
Microsoft MVP SQL Server
Culminis Speaker
"Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
news:uMtXDBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
> 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...
>

How to ignore error and continue trasactional replication

Hi,
I have a trasactional replication setup in SQL 2000 with SP3. Accidentally,
I deleted a row in the suscriber table. When I deleted the same row in the
publisher database, I have error in the replication monitor "the row was not
found at the Subcriber when applying the replicated command".
Please let me know how do I get rid of this error and continue replication.
I don't want to reinitialize the subscriber again because the table is big
and takes lot of time.
I appreciate your help!!
Thanks
Chinna.
gonzo - cowboy- to hell with database consistency approach - right click on
your failed agent, select agent profiles, and then select the continue on
data consistency profile.
more cautious approach. enable logging for your distribution agent, and
restart it. Find out the row which you deleted. Get this row from teh
publisher and manually construst the insert statement and put it back in the
subscriber. Restart your distribution agent.
check out this kb article for more info on how to do the logging.
http://support.microsoft.com/default...&Product=sql2k
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Chinna Kondaveeti" <Chinna Kondaveeti@.discussions.microsoft.com> wrote in
message news:4A2DEA01-1131-41EF-B432-6C26E923EBFA@.microsoft.com...
> Hi,
> I have a trasactional replication setup in SQL 2000 with SP3.
Accidentally,
> I deleted a row in the suscriber table. When I deleted the same row in the
> publisher database, I have error in the replication monitor "the row was
not
> found at the Subcriber when applying the replicated command".
> Please let me know how do I get rid of this error and continue
replication.
> I don't want to reinitialize the subscriber again because the table is big
> and takes lot of time.
> I appreciate your help!!
> Thanks
> Chinna.
>
|||Thanks to everyone who helped me. It worked!!. I have changed back to default.
I appreciate your help!!
Thanks
Chinna.
"Hilary Cotter" wrote:

> gonzo - cowboy- to hell with database consistency approach - right click on
> your failed agent, select agent profiles, and then select the continue on
> data consistency profile.
> more cautious approach. enable logging for your distribution agent, and
> restart it. Find out the row which you deleted. Get this row from teh
> publisher and manually construst the insert statement and put it back in the
> subscriber. Restart your distribution agent.
> check out this kb article for more info on how to do the logging.
> http://support.microsoft.com/default...&Product=sql2k
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Chinna Kondaveeti" <Chinna Kondaveeti@.discussions.microsoft.com> wrote in
> message news:4A2DEA01-1131-41EF-B432-6C26E923EBFA@.microsoft.com...
> Accidentally,
> not
> replication.
>
>