The information in this article applies to:
SUMMARYAn UPDATETEXT transaction will not be replicated if the process is not in the database that contains the updated table, even if it uses the "WITH LOG" option. The transaction must follow a "USE <database>" statement or a dummy update must be done on the table before the transaction can be replicated. MORE INFORMATION
The following scenario illustrates the problem:
processed 1 replicated transaction containing 0 commands. The distribution process will not be affected. Subsequent data modification statements will be replicated, and there will not be any operational discontinuity unless these operations refer to the data that was not replicated. The following code section explains the problem behavior (the section assumes that the "pub_info" table in "pubs" is published):
This will update the text value in pr_info column but will not be replicated. The updating process has to be in the pubs database during the updatetext call, which can be done by using "USE pubs" explicitly. In the case of a cross-database query, you can achieve this goal by using a dummy update inside the transaction that will set the process to be in the "pubs" database. The correct means of using UPDATETEXT for such cases would look as follows:
Additional query words: text replication
Keywords : SSrvProg SSrvRep SSrvTran_SQL kbbug6.50 |
Last Reviewed: April 1, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |