BUG: Filtered Stored Procedures for Horizontal Partitioning

Last reviewed: May 5, 1997
Article ID: Q152799
The information in this article applies to:
  • Microsoft SQL Server, version 6.0

SYMPTOMS

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.

WORKAROUND

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.

STATUS

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.


Additional query words:
Keywords : kbbug6.00
Version : 6.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.