Author: ReplTalk

Tune Replication Performance using PacketSize

Contributed 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 which inserts/updates
Read More »

All about “Identity Range Management”

José 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 topology that
Read More »

Navigating SQL Replication SubscriptionStreams setting

Rishi Maini | Microsoft SQL Escalation Services This blog posting discusses the new Distribution Agent SubscriptionStreams parameter.  This option reduces the latency when moving data from Distributor to Subscriber by using multiple parallel writer threads.  For more information on Replication “threads” see Transactional Replication Conversations blog posting. From SQL Books Online (good place to start)
Read More »

All about “Not for Replication”

Rishi Maini | Microsoft SQL Server Escalation Services All about “Not for Replication” “Not for Replication” is a property which can be set for different objects like Check constraints, Foreign Key constraints, Triggers , Identity columns etc while using SQL Server Replication. Feature used when the DBA would like the transactions to behave differently when
Read More »

The process could not execute ‘sp_repldone/sp_replcounters’

Anurag Sharma | Microsoft SQL Server Escalation Services Log Reader fails with below error message The process could not execute ‘sp_repldone/sp_replcounters’ on ‘SQLGUY’. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011) Get help: http://help/MSSQL_REPL20011 The log scan number (23:49:3) passed to log scan in database ‘PUBLISHER’ is not valid. This error may indicate data corruption or that the
Read More »