Microsoft KB Archive/258298

= BUG: WRITETEXT & UPDATETEXT Statements Fail When Run Against Snapshot Replication Tables =

Article ID: 258298

Article Last Modified on 10/16/2002

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q258298



BUG #: 57705 (SQLBUG_70)



SYMPTOMS
WRITETEXT and UPDATETEXT statements fail if you run the statements without the "WITH LOG" option against text or image columns that are being published for Snapshot Replication only. The error message that occurs is:

Server: Msg 7136, Level 16, State 1, Line 6

UPDATETEXT WITH NO LOG is not valid when the column is being replicated.



WORKAROUND
Use the "WITH LOG" option when you run the WRITETEXT and UPDATETEXT statements on columns that are being published for replication.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0.



MORE INFORMATION
By default, the WRITETEXT and UPDATETEXT run as "non logged" operations, which means that these transactions are not written to the database transaction log. To make these transactions "logged" operations, you must add the "WITH LOG" option in the statements.

Because Transactional replication needs to monitor the transaction log as part of the replication process, "non logged" operations are not supported for Transactional replication. For more information, see the SQL Server Books Online topic Provide support for text and image Data Types in Transactional Replication.

Snapshot Replication, however, applies changes to "publishing" tables by generating a new table snapshot for the tables that are being published. Snapshot replication process do not need to monitor the transaction log and hence, "non logged" operations are supported for Snapshot Replication tables.

However, if the same Snapshot replication table is also part of Transactional replication, you must use the "WITH LOG" option in all UPDATETEXT and WRITETEXT statements.

Keywords: kbbug kbpending KB258298

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.