How to call FullTextPopulation method?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Piotrek - 22 May 2006 12:36 GMT

Hi.

I would like to start population of Full Text Index from my stored
procedure. In SQL Books Online I found this: The FullTextPopulation
method starts or stops Microsoft Search full-text table population,
building the index supporting full-text queries on data maintained by
Microsoft® SQL Server 2000.

However, I have no idea how to call this method.

Does anybody know how to do it?

Thanks in advance,
Piotrek

Reply to this Message

Piotrek - 22 May 2006 13:45 GMT

One more thing: I am using Sql Server 2000.

Piotrek

Reply to this Message

Hilary Cotter - 22 May 2006 14:28 GMT

sp_fulltext_table 'tablename','start_full'

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> One more thing: I am using Sql Server 2000.
>
> Piotrek

Reply to this Message

Piotrek - 22 May 2006 14:36 GMT

Thanks Hilary.

It works great.

Piotrek

Reply to this Message

Piotrek - 23 May 2006 08:57 GMT

Hilary, could you explain me one more thing?

I have a table in which I added full text index on two columns. This
table has 1.500.000 rows. In addition this table has timestamp column.
Then I populated the index.
After population was finished, I added 10 new rows to indexed table and
I executed following statement: EXEC sp_fulltext_catalog
'IX_FT_Payments', 'start_incremental'.

I thought that it would be very fast, because I added only 10 rows.
However, index has been population for an hour and still this process
is not finished.

Why it takes so long?

Piotrek.

Reply to this Message

Daniel Crichton - 23 May 2006 10:50 GMT

Piotrek wrote on 23 May 2006 00:57:34 -0700:

> Hilary, could you explain me one more thing?
>
[quoted text clipped - 12 lines]
>
> Piotrek.

Incremental updates will reprocess the entire table looking for changes.
You're better off using Change Tracking - then only the rows that have had
updates will be processed.

Dan

Reply to this Message

Dave Poole - 26 May 2006 19:30 GMT

Also, if you don't want to use change_tracking you can speed up incremental
populations by creating an index on the timstamp column, this way the scan
can only look at the most recently changed rows.

Signature

Dave Poole
SQL Server Fulltext Team

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

> Piotrek wrote on 23 May 2006 00:57:34 -0700:
>
[quoted text clipped - 20 lines]
>
> Dan

Reply to this Message