BUG: Filtered Stored Procedures for Horizontal PartitioningID: Q152799
|
The Filtered Stored procedures used to facilitate Horizontal Partitioning in SQL Server 6.0 replication may not work when tables other than the one being published are involved in specifying the condition for the horizontal partition. The transaction fails to be recognized as a valid replicated transaction that should be distributed to the subscriber, even though the conditions for the horizontal partition are satisfied. The synchronization task has no problem in recognizing the satisfaction of the condition for partition. The logreader, however, reports in its history that it has processed a replicated transaction consisting of zero commands.
The entire table must be published without doing horizontal partitioning. If the partitioned data needs to be published, then you have to create a permanent table with the data from the original table selectively siphoned out (for instance, by using triggers with the partition condition) and then publish the new table.
Microsoft has confirmed this to be a problem in SQL Server 6.0. We are
researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
Keywords : kbbug6.00
Version : 6.0
Platform : WINDOWS
Issue type :
Last Reviewed: March 27, 1999