Here is a great posting by Kevin Locke on a problem he encountered when data modifications occurred near the top of a complicated replication filter configuration. These changes can cause “partition change” which triggers re-evaluation of all child data; also known as “repartitioning”. Kevin’s solution was to add an index to the Merge tracking tables,
Read More »
Sateesh Yele Microsoft SQL Server Support Transactional replication allows you to specify how data changes are propagated from the Publisher to Subscribers. For more information, please check this link. Specifying How Changes Are Propagated for Transactional Articles Recently, I worked on a case where the distribution agent failed with procedure was called with an incorrect
Read More »
ReplTip — Only one Log Reader can connect message when dropping a Publication by Taiyeb Zakir Sometimes when you try to drop a Transactional Publication using the GUI, you get the following error: Only one Log Reader Agent or log–related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you
Read More »