Article ID: 252372 - View products that this article applies to.
This article was previously published under Q252372
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56275 (SQLBUG_70)
If pull merge replication is set up using join filters in conjunction with login based dynamic filters as an intersection within the filter clause, the data on the publisher and subscriber may become unsynchronized.
The problem is that if the join filter uses the SUSER_SNAME function and if the merge task is using different logins for connecting to the Publisher and Subscriber, the merge agent does not expand the set of rows to be removed which then causes the non-convergence problem.
Run the pull merge agent on the subscriber with the same user context as the -PublisherLogin specified in the merge agent.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561For more information, contact your primary support provider.
(http://support.microsoft.com/kb/254561/ )INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
In order to produce a result that is an intersection of a join filter and a dynamic filter, the merge article is set up with dynamic filters specified in the join filter clause. For example:
With the preceding merge filter set up, if the PublisherLogin account is different from the user context under which the pull merge agent is running, when rows are deleted from table t2, the rows in table t1 that are connected to table t2 by join filter t1.ID=t2.ID are not removed.
Contact us for more help
Connect with Answer Desk for expert help.