September 25, 2005 at 6:41 pm
I have setup merge replication on SQL 2K between two 2k machines. I am using an anonymous subscription that accesses snapshots via http://FTP. Also, I have enabled dynamic filtering on all my articles.
When I insert a new row at the subscriber, the row is properly replicated to my publisher. The problem is, the new row is the deleted at the subscriber. I read on replicationanswers.com that when using filtered articles this is the default behavior. He provided 2 solutuions which are not acceptable at all(partitioned views or modifying the insert replication triggers) But this makes no sense at all. I wouldn't have used "Merge" replication if I wanted my databases to be out of sync. Am I missing something here? Why would anyone design replication that cuases the subscribers to be out of sync by default. I want changes made at my subscriber to be merged with my publisher and vice versa. I detect no error messages when this occurs so I assume I am just missing or not understanding some key info.
Any guidance would be greatly appreciated.
September 26, 2005 at 7:37 am
What does the conflict viewer reveal? This should contain a record of why the insert was rolled back.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
September 26, 2005 at 12:00 pm
Hi Hillary,
Thanks for the response. I took a look at the conflict viewer and it shows 2 issues with tables not related to the table I am having the problem with. i am investigating further to see if maybe these tables are playing a role in this problem.
On your site, you mentioned that this was the default behaviour for merge rep when using filtered articles, due to the fact that the filter is implemented via Views on the publisher which are not checked at the subscriber, etc. I didn't really understand the logic behind why this was the default behavior. Is this in fact the case or did I misunderstand the entry?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply