FIX: Filtered Stored Procedures Cannot Reference Multiple Tables
Article ID: 153186
Article Last Modified on 10/3/2003
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q153186
SYMPTOMS
The Filtered Stored procedures used to facilitate horizontal partitioning
in SQL Server 6.50 replication may cause the Logreader task to keep
retrying with the following message:
ConnectionTransact (GetOverLappedResult()).Possible network error:
Write to SQL Server. Failed. Connection broken.
This error prevents logreader from processing transactions, effectively
stopping replication. The problem occurs when rows that do not match the
restriction clause are inserted. This behavior is only exhibited in SQL
Server version 6.50.
WORKAROUND
To avoid encountering the bug you can:
- Publish the entire table instead of using horizontal partitioning.
-OR-
- Create a permanent table with the data from the original tables
selectively siphoned out (using triggers with the partition
condition) and then publish the new table.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.5. This problem was corrected in the latest Microsoft SQL Server
U.S. Service Pack. For information on obtaining the Service Pack, query on
the following word in the Microsoft Knowledge Base (without the spaces:)
S E R V P A C K
Additional query words: sp1
Keywords: kbfix kbnetwork KB153186