When SQL Server Replication Ignores Tables

Matt Slocum takes us through a tricky replication scenario (hint, they all are):

There are occasions when Updates, Inserts, and Deletes on a replicated table do not replicate out to the Subscriber.  You’ve verified that the table is listed in the Articles included in the Publication, and that there is at least one Subscription on the Publication. 

The strange thing is that there are likely other tables in the same Publication that are properly being replicated to the same Subscriber.

What is happening here?  Why is replication ignoring this table?

Read on to see Matt’s explanation and fix.

Related Posts

Conflict Tracking in Merge Replication

Ranga Babu shows the two different models for conflict detection with merge replication: Conflict Detection:The conflict detection depends on the type of tracking we configure for the article.– Row-level tracking: If data changes are made to any column on the same row at both ends, then it is considered a conflict.–Column-level tracking: If data changes are made […]

Read More

The Distribution Database and AGs

Andy Mallon looks at a wrinkle Availability Groups adds to replication: This has always worked super, and has been a go-to query for me for years. But when looking at a SQL Server 2017 distributor with the distribution database in an Availability Group, that wasn’t working. All the publications had a publisher_id of 1, but in sys.servers, server_id 1 […]

Read More

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Categories

April 2019
MTWTFSS
« Mar  
1234567
891011121314
15161718192021
22232425262728
2930