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.
Windows Server 2012 or Windows Server 2012 R2 Standard Edition is a great way to save thousands on licensing—and save yourself some serious headaches when deploying SQL Server AlwaysOn Availabiliity Groups....More
While I believe that NoSQL can have some places where it legitimately makes sense, I also believe that NoSQL is also the patently wrong choice for a number of different types of applications or use cases....More
Initial word on the street is that SQL Server 2014 has been very stable so far—which is probably why it went to release so quickly and bypassed what would typically have been another pre-release....More