Background

The following example shows how to do this by using Transact-SQL:

use dynamic_policy

sp_fulltext_table 'policy', 'start_background_updateindex'

go

Scheduled

As the name suggests, the job will run at a scheduled time. Please use the procedure mentioned under "Creating the Full-text Index for DynamicPolicy Documents" to schedule a Full Population by selecting the option "Schedules" instead of "Start Full-text Population". Follow the wizard to select the proper time and frequency for your organization.

If scheduled population is selected, one population per day is recommended during night ours.

For a production environment after the initial load of documents is published a background population could be enabled.

To determine the population status of a full-text catalog, run either of the following stored procedures:

sp_help_fulltext_catalogs [ @fulltext_catalog_name = ] 'fulltext_catalog_name'

-or-

SELECT fulltextcatalogproperty('%CatalogName%', 'PopulateStatus')

An integer value is returned for the status, which you can interpret by using the following list:

0 = Idle

1 = Full population in progress

2 = Paused

3 = Throttled

4 = Recovering

5 = Shutdown

6 = Incremental population in progress

7 = Building index

8 = Disk is full. Paused

9 = Change tracking