In Transactional Replication Subscriber reinitialization instructs the Distribution Agent to locate and distribute a NEW Snapshot to the Subscriber. In Merge Replication, the reinitialization is done by the Merge Agent. Depending on the Replication settings, the Subscriber tables may either be 1) dropped, deleted, or 3) truncated resulting in loss of data on the Subscriber.
Read More »
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 »
Transactional Replication Conversations When troubleshooting Transactional Replication performance break down the flow of data into 4 simultaneous conversation. Examine performance of each conversation. This will help verify where the bottleneck investigation should begin. 1) LogReader Reader thread is reading the Transaction Log via stored procedure sp_replcmds, a wrapper for xp_replcmds. It scans the transaction log
Read More »
We recently need to find all the difference in data between 2 SQL Servers each with 300 SQL replicated tables. To find the differences, we were planning on using the TableDiff utility included with SQL 2005 which is a command line tool designed to provide TSQL needed to manually sync two table in two different
Read More »
In this video •Configuring Distributor is first step in setting up SQL Server Replication •We verify Distributor is not configured •Walkthrough setting up SQL Replication Distributor using TSQL Scripts •Highlight of key parameters •Show how to generated Distributor TSQL commands automatically from SQL Server Management Studio Remember, you can double-click the video to view FULL
Read More »