mitra,
No, it's not just another job type operation... It more of "change log"
based, near real-time updating of the FT Catalog when the FT enable table's
columns changes. Also, it's not *directly* - Scheduled Job type - when used
with "Update Index in Background" (UIiB). This option is set via the
Enterprise Manager and by right-clicking on the table and selection Change
Tracking and then UIiB. Note, when you choose this option there is no need
to run a Full Population prior to setting this option as an automatic Full
Population will be started on an un-populated FT Catalog and if the FT
Catalog is populated, then an Incremental Population (assuming a timestamp
column in the table) will be started.
As for using a scheduled job and "Change Tracking", if you have a known
situation that you're planning to do a massive update or massive insertion
of many rows in to your FT enabled table that will also involve the FT
enable column, you may want - for performance reasons - to disenable UIiB,
while leaving "Change Tracking" enabled and then after your update, run an
Incremental Population JOB and then re-enable UIiB.
It's no problem if you don't have a timestamp column in your tables, as that
is what is best about "Change Tracking" and "Update Index in Background" as
it does not require a timestamp column. You just need to be aware that when
you attempt to run an Incremental population, you will in fact be running a
Full Population on those tables that do not have a timestamp column.
Large database, per se, are not a problem, it's sometimes an issue with the
specific tables that you want to FT enable that have many millions of rows
(usually >2 million) that can be problematic, but with careful tuning, and
the right hardware & software configurations, this too can be over come. See
SQL Server 2000 BOL title "Full-Text Search Recommendations" as a starting
point...
Regards,
John
[quoted text, click to view] "mitra fatholahi" <mitra928@hotmail.com> wrote in message
news:025601c352f2$d174c580$a601280a@phx.gbl...
> Hello Everyone,
>
> I read on SQL Server Books Online that the Incremental
> population for Full-Text Indexing:
>
> "requires that the indexed table have a column of the
> timestamp data type. If the table does not have a
> timestamp column, only full or change tracking populations
> can be performed. Requests for incremental populations on
> tables without timestamp columns result in a full
> population operation."
>
> Can someone please explain what is "change tracking
> populataions"? Is it just another job type option? If yes,
> how do i set the job type property of a catalog to "change
> tracking populations? I don't see this job type option
> anywhere on th eFull-Text Catalog Properties dialog box.
> I don't have a "timestamp" column in my table and our
> customer does not like to do a Full population since their
> database is very big.
>
> Thank you for your help!
>
> -Mitra
>
