The information in this article applies to:
BUG #: 54663 (SQLBUG_70) SYMPTOMSThe XCALL syntax option can be used when calling custom stored procedures. XCALL syntax specifies: "Stored procedures handling UPDATE statements will be passed the original (that is, the "before" image) values for all columns."However, if the update or delete takes place to an article with a published text or image column the Logreader can fail with this fatal message:
CAUSESQL Server 7.0 does not contain the previous text or image value(s) in a format the Logreader can currently obtain. However, Logreader did not account for this fact and fails while attempting to retrieve these values. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later: NOTE: Due to file dependencies, the most recent hot fix or feature that contains the above files may also contain additional files.STATUSMicrosoft has confirmed this to be a problem in SQL Server version 7.0. MORE INFORMATION
This hot fix correction accounts for the fact that previous values cannot be obtained and passes "NULL" as the previous value for any text or image column when using XCALL.
REFERENCESFor more details on XCALL, see SQL Server Books Online; topic: "Using Custom Stored Procedures in Articles"Additional query words:
Keywords : kbSQLServ700bug |
Last Reviewed: January 3, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |