Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am going to test this out, however I'd like to know what the forum would say.

I have 2 SQL servers with replication setup between them.

I am now adding another new SQL Server and I want this one to be the new publisher.

Do I need to recreate the databases on the old server when I setup replication again?

Can I simply stop subscription and then begin replicating from the new server to the same databases after I setup the machine?

share|improve this question
Wait, I'm confused. Is the new server going to be serving the same data as the old publisher, or will it be publishing something different? – swasheck Oct 1 '12 at 15:17
The same thing! But. It's SQL 2012 and the old server is 2005. – Dina Oct 1 '12 at 15:20
up vote 0 down vote accepted

Yes. After dropping the subscription, you will be able to simply configure replication from the new publisher to the existing subscriber. There is no need to drop the subscriber DB. Please bare in mind however that the subscriber will need to be re-initialized from the new publication. (Assuming transactional or merge publication) this can be achieved either through the snapshot agent or a backup/restore.

Also bare in mind that assuming your new publisher will also be your new distributor, you will need to configure this as well.

share|improve this answer
Agreed, also found instructions from MSDN: – Dina Oct 4 '12 at 18:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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