Reasons for replication latency over different data center and data domains

Vanitha Dodla (MINDTREE LIMITED) 40 Reputation points Microsoft Vendor

Issue is that on publisher, in replication monitor we are seeing replication is in sync, but our own monitoring which runs on the subscriber, reports that the column TIME in the table MSreplication_subscription is not updated and shows old value. How is this possible that on publisher replication is in sync and on subscriber it is not? What are some of the reasons for replication latency when working with different domains while same domain doesn't have any issue? Is there specific sp or commands or anything that we get alerts for latency issue happens and how to overcome this latency issues.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,309 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Olaf Helper 39,181 Reputation points

    That's more then a broad, if not very vague question. Do you really expect a specific answer? One reason: Bad network infrastructure.

    0 comments No comments

  2. CosmogHong-MSFT 20,826 Reputation points Microsoft Vendor

    Hi @Vanitha Dodla (MINDTREE LIMITED)

    If you need to modify the default intra-site domain controller replication interval, please refer to this doc: How to Modify the Default Intra-Site Domain Controller Replication Interval.

    Best regards,

    Cosmog Hong

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments