bi-directional transactional replication vs transactional replication with queued updating

Can someone help me understand the what the differences are between the
different types of bi-directional transactional replication, i.e
1) bi-directional transactional replication
2) transactional replication with queued updating,
Thanks
Bi-Directional replication is when a subscriber publishes back to the
publisher. You can only do this between two nodes, ie one publisher
subscriber pair. You need to partition carefully to minimize conflicts.
Queued updating using a queue (a SQL Server table or MSMQ). You can scale up
to about 10 clients - performance is not good after this. Queued updating
uses triggers on the subscriber and a tracking column.
HTH
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
"William F. Kinsley" <bacardi@.noemail.nospam> wrote in message
news:OABBHP4aFHA.2860@.TK2MSFTNGP10.phx.gbl...
> Can someone help me understand the what the differences are between the
> different types of bi-directional transactional replication, i.e
> 1) bi-directional transactional replication
> 2) transactional replication with queued updating,
> Thanks
>
>

Bidirectional replication

Hello,

is it possible to implement bidirectional replication with queued updating subscriptions in SQL Server 2000? I am currently testing bidirectional replication on two servers and it works well so far. My concern is how to I update the subscriber or publisher once both servers become disconnected? How to I resync? thank you for your help,

Lars

Bidirectinal replication does not support queued updating. But because both servers in bidirectional replication are publishers, if the two servers are disconnected, replication agents will just retry until it can connect to another server.

Keep in mind that bidirectional replication does not support conflict detection/handling.

Peng

|||

Thank you for the info!

L