BUG: Sp_replcmds Does Not Read the Replicated Command

Last reviewed: April 9, 1997
Article ID: Q160499
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16196

SYMPTOMS

The sp_replcmds stored procedure does not read the replicated transaction from the publisher's log when the command is a DBWRITETEXT statement issued against a text column of a published table. The transaction is logged in the publisher's log as a replicated transaction. This can be verified by using the stored procedures sp_repltrans and sp_replcmds. The WRITETEXT and UPDATETEXT commands work properly from Transact-SQL. Only the DBWRITETEXT command is not being replicated, even though the LOG option is used. The logreader issues the message "Processed 1 replicated transaction consisting of 0 commands" in the task history. The behavior is the same even when the DBWRITETEXT command is explicitly enclosed in a transaction using BEGIN and COMMIT TRAN statements run from the same DB-Library program.

WORKAROUND

Use the text and image functions in Transact-SQL (namely WRITETEXT and UPDATETEXT) with the LOG option, and enclose the text and image function calls within an explicit transaction.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: dblib db-lib t-sql
Keywords : kbbug6.50 kbusage SSrvDB_Lib SSrvRep SSrvStProc SSrvTran_SQL
Version : 6.5
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: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.