Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Replication (2005)
 All rows are not replicated correctly (merge)

Author  Topic 

sami273
Starting Member

9 Posts

Posted - 2007-09-28 : 08:15:07
Hi all! Hope you can help us with this one. We installed SP 2 of Sql server 2005 few months ago, and that caused a strange problem with merge replication.

We have about 150 subscribers in one merge publisher, and 200.000 new rows generated each day (retail system). Most tables are filtered.

Replication and filtering works fine, except 0,1% --> 0,2% of rows are not replicated correctly. These "problem-rows" are always replicated correctly to the publisher database, but publisher can't always replicate these rows further to other subscribers. Before SP2 everything worked fine.

Same problem occurs with filtered and non-filtered tables.

SQL Server shows no errors or warnings, everything SEEMS to work fine.

We have to make "dummy"-updates (like update SALES set id=id) in publisher database, to wake up the replicator. And always after these dummy updates all problem-rows will be replicated correctly from the publisher to subscribers.

Why do we have to "wake up" the replicator time to time with dummy updates? Is there a bug in SP2?

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-09-28 : 22:22:01
Did you see any conflict?
Go to Top of Page

sami273
Starting Member

9 Posts

Posted - 2007-09-29 : 06:12:27
Time to time there are few conflicts, but they are not related to problem rows any way. These conflicts are "legal", like simultaneous price updates, etc. There are no conflicts in transaction tables (we use only inserts there), and problem rows are typically in transaction data.

All foreign keys and triggers have "not for replication" -flag set on.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-09-29 : 21:43:06
Looks like time to call Microsoft support to see if it's known issue.
Go to Top of Page
   

- Advertisement -