I need to move my distributor server to a brand new server without resnapshotting it. The scenario I have is similar to the one defined in below link.



1 publisher 1 distributor 4 subscribers Replication type: Transactional replication with updatable subscription

I want to know if someone has tried the solution given in above link or if you have any alternate solution.

2 Answers 2


I didn't try this but just giving an approach I would follow.

The log reader scans all the log records and keeps it in distributor DB. The subscriber reads the records from the distributor DB, then inserts it in subscribers and marks the last record it read.

Considering the above topology, I don't see any issues with moving the distributor DB. Assuming you are moving the publisher(push) or subscriber(pull) involved and the server name remains the same.

In a Push model, the distributor DB resides in publisher and in pull model, the distributor resides in the subscriber DB.

Replication stores all the server information for all publishers, distributors, and subscribers in the database. So if you go with this approach I would suggest the below steps:

  1. Stop all jobs (log reader, distributor)
  2. Move all databases(attach, detach) to new server with same server name

The only issue I see here is the instance name being the same as the old one, which can be tricky. You also can try testing this yourself with a single table replication and with the same setup.


If you have VmWare or Hyper-V and assuming your current distributor is a physical server you can move it to a virtual server. I believe VMWare's utility is called p2V and MS should have something similar for Hyper-V where it copies the server to the new one. Applications and all. I think the only limitation is that you have to shut down the old server.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.