Article ID: 304551
Article Last Modified on 10/16/2003
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition
This article was previously published under Q304551
BUG #: 354724 (SHILOH_BUGS)
SYMPTOMS
When making updates at the subscriber of a merge publication with vertical filters, the changes may not be sent to the publisher when the merge agent runs.
This problem is encountered if all of the following conditions are met:
- A column after the 8th column in the table is filtered out.
- The update is being issued at the subscriber for a column after the 8th column that is included in the subscriber's vertical partition.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
Hotfix
NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.
The English version of this fix should have the following file attributes or later:
File name Platform
-----------------------
s80420i.exe x86
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
MORE INFORMATION
When a row is updated at the subscriber, the change is recorded in the merge replication system tables. The change is then detected and uploaded to the publisher when the merge agent runs. The change is tracked at both the row level and at the column level (in terms of versions).
Any change (update) to a column other than the first 8 columns will cause incorrect tracking at the column level. That in turn will cause the merge agent to send a "dummy" update statment to the publisher, which leads to nonconvergence.
Keywords: kbbug kbfix kbsqlserv2000presp2fix KB304551
