FIX: NO SYNC on Snapshot Allows Transactions To Be Distributed

• Microsoft SQL Server, version 6.0

SYMPTOMS

If you subscribe to a publication that is setup for "Scheduled Table Refresh" (for example, a snapshot) specifying "No Synchronization," any changes to the publication will be sent to the subscriber as log-based replication transactions. No data should be sent to the subscriber under this configuration.

WORKAROUND

Subscribe to the publication using a sync method of "Automatic Synchronization."

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.0. For more information, contact your primary support provider.

MORE INFORMATION

When a publication is defined for a frequency of "Scheduled Table Refresh," the only subscription method that should be selected is "Automatic Synchronization." The SYNC task for each publication is responsible for generating the proper schema script and data file to perform the table refresh. If you select "No Synchronization" then no table refresh should be allowed, therefore no data should be sent to the subscriber. Likewise, if you select "Manual Synchronization" then manual intervention would be required for each table refresh.