Microsoft KB Archive/321852

= DOC: Loopback_detection Option is Not Clearly Explained in SQL Server Books Online =

Article ID: 321852

Article Last Modified on 10/9/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q321852



BUG #: 357065 (SHILOH_BUGS)



SUMMARY
The following text is in the sp_addsubscription section of SQL Server Books Online: [@loopback_detection = ] 'loopback_detection'

Specifies if the Distribution Agent sends transactions that originated at the Subscriber back to the Subscriber. loopback_detection is nvarchar(5), and can be one of these values:

The preceding text implies that you can set the @loopback_detection option to TRUE only if:


 * The subscription is an Immediate Updating subscription (@update_mode= 'sync tran'). -and-


 * A published timestamp column exists in the table.

However, that statement is not completely true. The following section provides you with more information about the correct usage of the @loopback_detection option:

By default, subscription level loopback_detection is only set on for updateable subscriptions (immediate or queued). It is left as &quot;false&quot; for read-only subscribers. However, that does not mean that you cannot turn the option on for read-only subscriptions. The @loopback_detection option is used for bi-directional replication. The @loopback_detection option tells the Distribution Agent not to apply subscriber-originated commands back to the same subscriber.



STATUS
Microsoft has confirmed that this is a problem in SQL Server 2000 Books Online.

Microsoft has confirmed that this is a problem in SQL Server 7.0 Books Online.

Keywords: kbbug kbpending KB321852

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.