Solution for “nightly batch” and Transactional Replication

“We need to reload a table weekly\nightly, batch job takes few minutes, but Replication takes long time to move the batch changes to Subscriber, how can we speed this up”? If Subscriber is mirror of Publisher, perhaps Replication is the wrong technology! A better solution may be to configure the database for AlwaysOn Availability Groups…


Impact of large batch on Transactional Replication topology

Chris SkorlinskiMicrosoft SQL Server Escalation Services Every write an update statement touching +50 million commands in a single transaction? Ever on a table being Published in Transaction Replication? How about to a subscriber half way around the world or on a satellite connected network? While nothing in Replication design prevents, there may be challenges that…


Distribution Agent fails with ‘Cannot update identity column ‘OrderID’.’

Chris SkorlinskiMicrosoft SQL Escalation Services I wanted to share this problem which started down a “your data is wrong” path, but ended up with “your customer scripts to create Transactional Replication need to be tweaked”. Customer reported the following error in Replication Monitor: Cannot update identity column ‘OrderID’. Looks like Distribution Agent is trying to…


Script to decrypt the @schema_option for a Transactional Replication Article

Chris SkorlinskiMicrosoft SQL Server Escalation Services The code below helps decrypt @schema_option settings for Transaction Replication articles. Note the meaning of binary offset may change in future builds of SQL Server. Always check Microsoft docs for most accurate listing. You’ll find scheme_options listing documented at sp_addarticle. Code for this example now posted on https://github.com/ReplTalk/ReplScripts/blob/master/schema_option.sql Example:…