Records modifications in the text_events table when you change the text index’s source table data.
sp_refresh_text_index table_name, column_name, rowid, mod_type
– is the name of the source table being updated. table_name has the form [dbname.[owner.]]table, where:
dbname is the name of the database containing the table.
owner is the name of the owner of the table.
table is the name of the table.
– is the name of the column being updated.
– is the IDENTITY column value of the changed row.
– specifies the type of the change. Must be insert, update, or delete.
sp_refresh_text_index "blurbs", "copy", 2.000000, "update"
Records in the text_events table that you have updated the copy column of the blurbs table. The row you have updated has an id of 2.000000.
The user maintains the consistency of the text index. You must run sp_refresh_text_index anytime you update source data that has been indexed so that the text_events table reflects the change. This keeps the collections in sync with your source data. The collections are not updated until you run sp_text_notify.
You can create triggers that issue sp_refresh_text_index for non-text and non-image columns. For more information on creating triggers, see “Propagating Changes to the Text Index”.
Column ’column_name’ does not exist in table ’table_name’
Invalid mod_type specified (’mod_type’). Correct values: INSERT, UPDATE, DELETE
Owner ’owner_name’ does not exist
Table ’table_name’ does not exist
’table_name’ is not a valid name.
Text event table not found
Any user can execute sp_refresh_text_index.
