Share this PostJosé Moreira Neto | Microsoft SQL Server Escalation Services Problem 1: batch updates 1) A single update command can generate a transaction with thousands of commands. For example if you execute an UPDATE statement that updates 10K rows on the publisher, up to 20K commands can be send over to the subscriber. On
Read More »
Share this PostContributed by: Karol Korasadowicz Depending on type of data being replicated and network throughput adjusting the PacketSize parameter for the Distribution Agent may increase your overall Transactional Replication performance. -PacketSize packet_size Is the packet size, in bytes. The default is 4096 (bytes). http://msdn.microsoft.com/en-us/library/ms147328.aspx To see which setting has most impact, create test scenario
Read More »
Share this PostAs we know, Transactional Replication moves data from the Publisher to the Distributor then to the Subscribers. When working, data flows near real-time through both of these steps. When problems occur which interrupt this flow, latency is introduced. The challenge is to find which step is contributing to the overall latency. Tracer Tokens
Read More »
Share this PostJosé Moreira Neto | SQL Server Escalation Services Automatic Identity Range Management Microsoft SQL Server automatically generates sequential numbers for new rows inserted in the table containing the identity column. Identity columns are normally included as part of Primary Keys, therefore the need to avoid duplicates. To use identity columns in a replication
Read More »
Share this PostBalakrishnan Shankar | Microsoft SQL Server Escalation Services During the course of troubleshooting, Microsoft SQL Support team we collect from customers the Publication Creation Script. In cases involving Snapshot generation and application problems, it might become necessary to decrypt the schema options for an article from customer’s script. Below script will help deduce
Read More »