title: SQL Server 2008R2 Transactional Replication - Move SubscriberDB - Push Subscription
body: <p>SQL Server 2008R2 Transactional Replication - Move SubscriberDB - Push Subscription</p>
  
  <p>I have a requirement to move a subscriber database to a new server outside of a system outage i.e. I cannot stop new transaction from loading into the publisher database. </p>
  
  <p>So far I have attempted to stop the distribution agent and let all un-replicated commands replicate to the subscriber database at Server1. Then backup and restore the subscriber database to Server2.  I have then created a new subscription from Server2 to the existing publication. </p>
  
  <p>This works but only transactions created from that point forward are replicated to the Server2 subscriber database. I also require all the old transactions built up at the distributor database destined to only go to Server1. </p>
  
  <p>Is there a replication command available to update the destination of existing transactions at the distributer to the new subscriber.subscriber_DB? </p>
  
  <p>There is 1 publication with multiple articles. The publication is currently only subscribed to by one database at Server1.  </p>