Note
ამ გვერდზე წვდომა ავტორიზაციას მოითხოვს. შეგიძლიათ სცადოთ შესვლა ან დირექტორიების შეცვლა.
ამ გვერდზე წვდომა ავტორიზაციას მოითხოვს. შეგიძლიათ სცადოთ დირექტორიების შეცვლა.
Applies to: 
SQL Server
Azure SQL Managed Instance
Bidirectional transactional replication is a specific transactional replication topology that allows two servers to exchange changes with each other: each server publishes data and then subscribes to a publication with the same data from the other server. Set the @loopback_detection parameter of sp_addsubscription (Transact-SQL) to TRUE to ensure that changes are only sent to the Subscriber and don't result in the change being sent back to the Publisher.
In SQL Server 2005 (9.x) and later versions, peer-to-peer transactional replication also supports this topology, but bidirectional replication can provide improved performance.
To add a subscription to a bi-directional publication by using the fully qualified domain name (FQDN), verify that the server name (@@SERVERNAME) of the subscriber returns the FQDN. If the subscriber server name doesn't return the FQDN, changes that originate from that subscriber might cause primary key violations.