I have Transactional replication from SQL Server 2016 to remote SQL Server 2016.
Publisher and Distributor on local server, Subscription on remote server.
Using Alias=Server Name, Server=IP Address, Protocol=tcp, Parameters=1433 I can successfully replicate to remote SQL Server database.
New requirements being proposed would have 1) Existing connection for on-going transactional replication and 2) new VPN connection with a different IP Address from the IP Address in #1 to be used for initial population of replicated tables due to large volume.
When I tried setting up a second Alias using a different IP Address but keeping the other information the same it updated the IP Address for the existing Alias.
If I have to switch the IP Address of the server between the 2 pipes being used will this require a complete refresh of the Subscription each time I switch or will replication just keep on going?
Is there anything else I need to consider when doing this?
Thanks!
Publisher and Distributor on local server, Subscription on remote server.
Using Alias=Server Name, Server=IP Address, Protocol=tcp, Parameters=1433 I can successfully replicate to remote SQL Server database.
New requirements being proposed would have 1) Existing connection for on-going transactional replication and 2) new VPN connection with a different IP Address from the IP Address in #1 to be used for initial population of replicated tables due to large volume.
When I tried setting up a second Alias using a different IP Address but keeping the other information the same it updated the IP Address for the existing Alias.
If I have to switch the IP Address of the server between the 2 pipes being used will this require a complete refresh of the Subscription each time I switch or will replication just keep on going?
Is there anything else I need to consider when doing this?
Thanks!