To enable a database for full-text indexingDigital information is stored in both database columns and in the file system as unstructured data, primarily text. Some text data is stored in database character-type columns as well. For example, in Microsoft® SQL Server™, such data can be stored in database columns with the char, varchar, text, ntext, nchar, or nvarchar data types.
Consequently, a method for retrieving this text data from the database is needed. Relational database management systems traditionally have had limited capabilities for finding patterns in textual data. For example, a system may be able to retrieve text based on pattern matching, but cannot handle searches that look up words and phrases in close proximity to one another.
Previously, corporate users of relational database management systems had to buy expensive third-party offerings to retrieve or query data stored in these character-based database columns. These solutions typically involved a two-step process:
Using this two-step process meant that there was no seamless way for combining a full-text query with a regular, structured relational query. SQL Server solves this problem by allowing full-text queries to be issued against plain character-based data in SQL Server tables, including words and phrases, or multiple forms of a word or phrase.
To enable a database for full-text indexing
To enable a table for full-text indexing
To enable a column for full-text indexing
To edit a full-text index on a table
To remove full-text indexing from a table
To create a full-text catalog
To rebuild a full-text catalog
To rebuild all full-text catalogs in a database
To start and stop a full or incremental population of a full-text index
To check the status, tables, and schedules of a full-text catalog
To change or create a new schedule for a full-text catalog
To remove a full-text catalog from a database
To remove all full-text catalogs in a database
To clean up the full-text catalogs on a server
To repopulate all full-text catalogs for a database