SQL server transactional replication, change distribution server -


i have sql 2005 database published dozens of (mostly) transactional publications , dozens of subscribers . have local distributor. i'm trying improve our ha setup , looking @ mirroring published database. best practices use remote distributor, in case have fail on mirror replication can continue. i've tested , works fine.

but if remote distributor fails? how eliminate single point of failure, or better, how recover when fail?

from testing , little find on web, need undo replication set (remove subscribers, articles & publications, distributor) , recreate new remote distributor specified. i'd fine if add subscribers without needing reinitialize them. i've used @subscriptionlsn input of sp_addsubscription similar situations, want resume replication without resnapshoting & reinitializing them . undoing replication, min_autosynch_lsn lost outstanding transactions go it.

i must missing fundamental. know clustering distributor adds layer of safety, fail. how, or can, switch different distributor without reinitializing data on them?

there isn't answer.

other replication technologies tungsten replicator , built in mysql , postgresql replication don't have need central distribution server since both take advantage of reading binlog on subscriber.

i have found following bol regarding dr replication topologies.

technet replication paper


Comments

Popular posts from this blog

wordpress - (T_ENDFOREACH) php error -

Export Excel workseet into txt file using vba - (text and numbers with formulas) -

Using django-mptt to get only the categories that have items -