FIX: Incorrect Per-Article Contents BCP for Dynamic Snapshot (308740)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q308740
BUG #: 355047 (SHILOH_BUGS)

SYMPTOMS

When the Snapshot Agent generates per-article contents BCP files, SQL Server does not account for the dynamic snapshot. Consequently, the MSmerge_contents rows that SQL Server bulk-copies out for the dynamic snapshot are incorrect in the per-article contents BCP file generation case, which may cause a subscriber to have incorrect information in the MSmerge_contents table, thus causing one or more of the following problems:

  • Longer run duration for the initial Merge Agent execution when you apply the dynamic snapshot.
  • Spurious conflicts.
  • Unexpected conflict resolution outcomes.

CAUSE

SQL Server does not pass the list of dynamic snapshot views into the sp_MSmakectsviews stored procedure while the dynamic snapshot is in process, thus the per-article contents bcp that SQL Server generates does not conform the dynamic filtering criteria. In particular, this affects cases where you use the login name in the dynamic filters.

SQL Server uses the per-article contents bcp generation when the number of articles is more than 256 and/or complex join filters are part of the publication.

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

STATUS

Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Modification Type:MajorLast Reviewed:10/16/2003
Keywords:kbbug kbfix KB308740