We are looking into upgrading our SQL 2008 remote distributor to SQL 2014. Our publication tables have heavy selects on them. Every time we have to resnap we have to shut down the apps so that replication can finish. Our sync_method is 3 in the syspublications table (Concurrent, which means that native-mode BCP is used but tables are not locked during the snapshot). For our upgrade, we need to have no downtime since replication is critical to our environment. One option we have is to create a new SQL 2014 distributor and slowly move over our publications. However, we are concerned that we will be taking outages due to replication resnapshots needed when we recreate the publication that are blocked and block other connections. Is there any way to achieve what we want to do?
↧