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.
There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More
Code like this isn’t optimal:
IF EXISTS(SELECT * FROM sys.objects WHERE name = N'TableToDrop' AND type = 'U')
DROP TABLE TableToDrop;
Neither is this:
IF EXISTS(SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'TableToDrop')
DROP TABLE TableToDrop;
Yet, I see both of those used all of the time – over and over again. Even though it’s 2015. ...More
This blog post is a bit of a ‘repeat’ – since I already covered much of the rationale behind this post in Part 23 of my multi-part series on AlwaysOn Availability Groups and SQL Server Agent Jobs. But, I also figured that this is enough of an important topic to merit its own blog post....More