Server Fault is a question and answer site for system and network administrators. 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

Info Server A – Windows 2003 with SQL 2005 SP3 Server B – Windows 2008 with SQL 2005 SP3

Server A is running transactional replication for 20 articles of 30 articles with 30 subscribers in different time zones and wan speeds that have been created with a snapshot. Server A is the distribution server also.

Server B is a new server to replace Server A. Server B will be renamed to the same name as Server A, once Server A has stopped replication and renamed.

Question: How could I recreate the transactional replication without having the snapshots get pushed down again. There will be no data changes while this move is taking place. I cannot do the backup publishers method since there are 10 tables not replicated.

share|improve this question

If when you build the new server you put the database files all in the same path, you can copy all the system and user database files into place. This way when the new server comes online it should come up with the replication still in place.

Keep in mind that this isn't going to be a Microsoft supported solution. The supported solution would be to repush the snapshots after configuring replication on the new system.

This only works because you are planning on using the same build of SQL Server on the new machine.

share|improve this answer
If the new server was built from scratch (not restore of the old server's DBs) the LSNs and XactIds of the new publisher DB will not match the data in the distribution db and log reader will go ballistic. – Remus Rusanu Nov 2 '10 at 0:12

Your Answer


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