moving distribution database to a separate server

Heisenberg 261 Reputation points

hi all,
SQL 2014.
Currently we have always on setup with primary and secondary servers. At the same time our primary server is also a publisher and host distributor too. We are planning to move distributor to a separate dedicated server. My question is , if we do this will we run into any replication latency? any particular configuration that need to be taken care of in this setup to avoid any 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,851 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. YufeiShao-msft 7,061 Reputation points

    Hi @SQLServerBro,

    It depends on the workload and the hardware in question, having the distributor on another server means that part of the buffer pool will be getting used by the distribution database and then there is the CPU and memory needed by all the agents that you are running

    There is a articles for Moving Distribution Database and troubleshooting for possible latency issuses


    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.