Transactional replication with queued updates (TRQU) can be a useful way to replicate data if you can tolerate some latency. Sameer Dandage examines the intricacies of backing up and restoring TRQU setups.
In transactional replication with queued updates (TRQU), the Distributor needs to connect to the Publisher and Subscriber. For security, the replication agents use a special SQL Server login that SQL Server creates during the replication setup for this purpose. This login, distributor_admin, has sysadmin permissions on all SQL Server instances involved in the replication process. You can see this login in the sysxlogins table on all servers.
Maintaining multiple database servers at multiple sites in active mode and closely synchronizing copies of the data on all servers is a challenge for any DBA. But as long as you can tolerate a little latency, one good option for keeping your data current at all locations is to use SQL Server’s transactional replication with queued updates (TRQU). In the first article in this series, “Queuing Up,” December 2003, InstantDoc 40567, I showed how to set up TRQU.
If you need to maintain multiple database servers at multiple sites and synchronize all the data, SQL Server has a solution to make your job easier--SQL Server’s Transactional Replication with Queued Updates can help.
When compared to AlwaysOn Failover Cluster Instances or clustered deployments of SQL Server, one of the main problems with AlwaysOn AGs is that a single database is made to straddle multiple hosts....More