Home Dashboard Directory Help

Issue with 2 way in replication by Alexandre Tavares


 as Not Reproducible Help for as Not Reproducible

Sign in
to vote
Type: Bug
ID: 377555
Opened: 10/24/2008 6:13:25 AM
Access Restriction: Public
User(s) can reproduce this bug


Replication insn´t working fine.

Dear Alexandre,

Thank you for the update.

I understand how urgent the case. We are still communicating with our
development team and didn't get a clear alternative method to make
replication that you want to designed. Please rest assured we will try our
best to help you to work on the case.

Besides the above info, if you have any feedback or wishes on SQL Server, I
encourage you submit via the link below and our product team would like to
hear your voice:


Thank you for your patience!

Best Regards,

Robbie Meng
Microsoft Online Partner Support
Sign in to post a comment.
Posted by Microsoft on 1/4/2012 at 5:49 PM
Hi Alexandre ,

I am cleaning up very old issues which have been inactive for many years.
Please reopen a new one if the issue is still relevant to you and share updated information. I'm following up on new entries on a regular basis.

Thanks for taking the time to share your feedback, this is really important to us.

Best regards
Jean-Yves Devant
Program Manager (Replication/CDC/CT)
SQL Server Engine Team
Posted by Microsoft on 1/12/2009 at 4:27 PM
Dear Alexandre,
Thanks for reporting this issue thru the Microsoft connect program. I need some additional information for me to better diagnose what might be a problem in your particular environment. First, let me make sure I have the scenario defined correctly.
•    Tran replication setup between FILIAL02 -> MATRIZ for table TABLE_SALES
•    Trigger at MATRIZ on TABLE_SALES inserts changes into TABLE_SALES_TEMP
•    Tran replication setup between MATRIZ -> FILIAL01 and MATRIZ - > FILIAL02 for TABLE_SALES_TEMP

Problem: not seeing changes in TABLE_SALES_TEMP on FILIAL02

Based on what you have told me so far replication is working fine to TABLE_SALES_TEMP on FILIAL01 so we know the changes are being harvested from the log on MATRIZ and placed in the distribution database. We also know the distribution of changes is happening for FILIAL01 which means the distribution agent is running for this subscription. We need to focus on the distribution agent for FILIAL02 subscription. First thing is to verify the distribution agent is being started (verify in distribution history table at the distributor). If it is running/started, see if there are any errors in the distribution history for this subscription. You can do this by running the distrib.exe from the command line or look at the distribution history for this subscription (if you run from command line turn -historyverboselevel 2). If you’re not finding anything from this exercise, try reinit’ing the FILIAL02 subscription and watch it proceed thru the various stages (remember to rerun the snapshot agent if immediate sync is not turned on) to see any of the initialization steps are failing. Once you gather this information please post back your findings in hopes of finding a resolution to your issue.

Sign in to post a workaround.
Posted by agentritter on 6/2/2010 at 2:59 PM
SQL Server 2008 has a different definition of loopback detection. In SS2000, the same table would need to be replicated bidirectionally in order to be protected from a replicated loopback. In SS2008, the result of a replicated transaction cannot replicate back to the originating publisher no matter what tables are affected by the result.

To get around this problem I have to explicitly set @loopback_detection = 'false' in the call to sp_addsubscription. Keep in mind that @loopback_detection = 'true' is the default argument in SS2008.

File Name Submitted By Submitted On File Size  
Replication Diagram.pdf (restricted) 10/24/2008 -