Full-text administration for a server instance includes:
System management tasks such as managing the FDHOST Launcher service (MSSQLFDLauncher), restarting filter daemon host process if you change the service account credentials, configuring server-wide full-text properties, and backing up full-text catalogs. At the server level, for example, you can specify a default full-text language that differs from the default language of the server instance as a whole.
Configuring full-text linguistic components (word breakers and stemmers, thesaurus file, and stopwords and stoplists).
Configuring a user database for full-text search. This involves creating one or more full-text catalogs for the database and defining a full-text index on each table or indexed view on which you want to execute full-text queries.
You can view the full-text properties of an instance of SQL Server in SQL Server Management Studio.
To view and change server properties for full-text search
In Object Explorer, right-click a server, and then click Properties.
In the Server Properties dialog box, click the Advanced page to view server information about full-text search. The full-text properties are as follows:
Default Full-Text Language
Specifies a default language for full-text indexed columns. Linguistic analysis of full-text indexed data is dependent on the language of the data. The default value of this option is the language of the server. For the language that corresponds to the displayed setting, see sys.fulltext_languages (Transact-SQL).
Full-Text Upgrade Option
This server property controls how full-text indexes are migrated when upgrading a database from SQL Server 2005 to a later version. This property applies to upgrading by attaching a database, restoring a database backup, restoring a file backup, or copying the database by using the Copy Database Wizard.
The alternatives are as follows:
Full-text catalogs are imported. Typically, import is significantly faster than rebuild. For example, when using only one CPU, import runs about 10 times faster than rebuild. However, an imported full-text catalog does not use the new and enhanced word breakers introduced in SQL Server 2008, so you might want to rebuild your full-text catalogs eventually.
Rebuild can run in multi-threaded mode, and if more than 10 CPUs are available, rebuild might run faster than import if you allow rebuild to use all of the CPUs.
If a full-text catalog is not available, the associated full-text indexes are rebuilt. This option is available for only SQL Server 2005 databases.
Full-text catalogs are rebuilt using the new and enhanced word breakers. Rebuilding indexes can take awhile, and a significant amount of CPU and memory might be required after the upgrade.
Full-text catalogs are reset. SQL Server 2005 full-text catalog files are removed, but the metadata for full-text catalogs and full-text indexes is retained. After being upgraded, all full-text indexes are disabled for change tracking and crawls are not started automatically. The catalog will remain empty until you manually issue a full population, after the upgrade completes.
For information about choosing a full-text upgrade option, see full-Upgrade Full-Text Search.
The full-text upgrade option can also be set by using the sp_fulltext_serviceupgrade_option action.
Transact-SQL functions can be used to obtain the value of various server-level properties of full-text search. This information is useful for administrating and troubleshooting full-text search.
The following table lists full-text properties of a SQL Server server instance and their related Transact-SQL functions.
|IsFullTextInstalled||Whether the full-text component is installed with the current instance of SQL Server.||FULLTEXTSERVICEPROPERTY
|LoadOSResources||Whether operating system word breakers and filters are registered and used with this instance of SQL Server.||FULLTEXTSERVICEPROPERTY|
|VerifySignature||Specifies whether only signed binaries are loaded by the Full-Text Engine.||FULLTEXTSERVICEPROPERTY|
Several dynamic management views and functions are useful monitoring full-text search activity on a server instance.
To view information about the full-text catalogs with in-progress population activity
To view current activity of a filter daemon host process
To view information about in-progress index populations
To view memory buffers in a memory pool that are used as part of a crawl or crawl range.
To view the shared memory pools available to the full-text gatherer component for a full-text crawl or a full-text crawl range
To view information about each full-text indexing batch
To view information about the specific ranges related to an in-progress population