Applies To: SQL Server 2014, SQL Server 2016 Preview
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Is a one- or two-part table name. The table must exist in the current database. qualified_table_name is nvarchar(517), with no default.
[ @action=] 'action'
Is the action to be performed. action is nvarchar(50), with no default, and can be one of these values.
Creates the metadata for a full-text index for the table referenced by qualified_table_name and specifies that the full-text index data for this table should reside in fulltext_catalog_name. This action also designates the use of unique_index_name as the full-text key column. This unique index must already be present and must be defined on one column of the table.
A full-text search cannot be performed against this table until the full-text catalog is populated.
Drops the metadata on the full-text index for qualified_table_name. If the full-text index is active, it is automatically deactivated before being dropped. It is not necessary to remove columns before dropping the full-text index.
Activates the ability for full-text index data to be gathered for qualified_table_name, after it has been deactivated. There must be at least one column participating in the full-text index before it can be activated.
A full-text index is automatically made active (for population) as soon as the first column is added for indexing. If the last column is dropped from the index, the index becomes inactive. If change tracking is on, activating an inactive index starts a new population.
Note that this does not actually populate the full-text index, but simply registers the table in the full-text catalog in the file system so that rows from qualified_table_name can be retrieved during the next full-text index population.
Deactivates the full-text index for qualified_table_name so that full-text index data can no longer be gathered for the qualified_table_name. The full-text index metadata remains and the table can be reactivated.
If change tracking is on, deactivating an active index freezes the state of the index: any ongoing population is stopped, and no more changes are propagated to the index.
Start an incremental population of the full-text index. If the table does not have a timestamp, start a full population of the full-text index. Start tracking changes to the table.
Full-text change tracking does not track any WRITETEXT or UPDATETEXT operations performed on full-text indexed columns that are of type image, text, or ntext.
Stop tracking changes to the table.
Propagate the current set of tracked changes to the full-text index.
Start propagating tracked changes to the full-text index as they occur.
Stop propagating tracked changes to the full-text index as they occur.
Start a full population of the full-text index for the table.
Start an incremental population of the full-text index for the table.
Stop a full or incremental population.
[ @ftcat=] 'fulltext_catalog_name'
Is a valid, existing full-text catalog name for a create action. For all other actions, this parameter must be NULL. fulltext_catalog_name is sysname, with a default of NULL.
[ @keyname=] 'unique_index_name'
Is a valid single-key-column, unique nonnullable index on qualified_table_name for a create action. For all other actions, this parameter must be NULL. unique_index_name is sysname, with a default of NULL.
After a full-text index is deactivated for a particular table, the existing full-text index remains in place until the next full population; however, this index is not used because Microsoft SQL Server blocks queries on deactivated tables.
If the table is reactivated and the index is not repopulated, the old index is still available for queries against any remaining, but not new, full-text enabled columns. Data from deleted columns are matched in queries that specify an all-full-text column search.
After a table has been defined for full-text indexing, switching the full-text unique key column from one data type to another, either by changing the data type of that column or changing the full-text unique key from one column to another, without a full repopulation may cause a failure to occur during a subsequent query and returning the error message: "Conversion to type data_type failed for full-text search key value key_value." To prevent this, drop the full-text definition for this table using the drop action of sp_fulltext_table and redefine it using sp_fulltext_table and sp_fulltext_column.
The full-text key column must be defined to be 900 bytes or less. It is recommended that the size of the key column be as small as possible for performance reasons.
The following example creates full-text index metadata for the Document table of the AdventureWorks database. Cat_Desc is a full-text catalog. PK_Document_DocumentID is a unique, single-column index on Document.
EXEC sp_fulltext_table 'Production.Document', 'create', 'Cat_Desc', 'PK_Document_DocumentID';
--Add some columns
EXEC sp_fulltext_column 'Production.Document','DocumentSummary','add';
-- Activate the full-text index
EXEC sp_fulltext_table 'Production.Document','activate';
B. Activating and propagating track changes
The following example activates and starts propagating tracked changes to the full-text index as they occur.