Indexing too slow?

I have a simple search engine applicaton. Everytime a search is being
made I look in the database using a simple select query if the keyword
has been searched for in the last week. If not, I then go out and
search a number of websites using a httprequest, parse out and insert
the results into my catalog table (which has a fulltext index). Right
after I insert the rows into the table I use a CONTAINSTABLE query to
pull the results I just added and anything else that matches that has
already been added to the table from previous search results.

The problem is that the latest search results are not indexed fast
enough. So when I add the latest results and run the CONTAINSTABLE
query my latest results are not included. If I however put the thread
to sleep for 2 seconds and then execute the query my latest additions
do show up.

My queston is, is there a way to do this without using the thread
sleep? Is there a way to index my results instantly and making them
available without using a 2 second pause? Has anyone else had similar
problems?

Any advice is highly appreciated. Thanks for your help.

Nightcrawler,

Full-text indexing is asynchronous to your updates, so I don't believe there
is a way to avoid the delay. (And asynchronous is good for things that take
time, like parsing a string apart, filtering it for noise words, then adding
0 to thousands of entries to the full-text index. I would not like to wait
for that to happen to me on every update.)

I believe that SQL Server 2005 has proved to be faster than SQL Server 2000.
And Simon Sabin's blog suggest improvements in SQL Server 2008. But I am
unaware of anybody saying that full-text indexing is instantaneous.
http://sqlblogcasts.com/blogs/simons/archive/2008/02/20/SQL-Server-200...-iFTS-P

I might compare triggering the full-text indexing of a new or updated row to
putting an update trigger on a table that starts a SQL Agent job. This
trigger fires immediately on the update, but the SQL Agent job takes some
asynchronous time to get its part done.

RLF

"Nightcrawler" wrote in message

>I have a simple search engine applicaton. Everytime a search is being
> made I look in the database using a simple select query if the keyword
> has been searched for in the last week. If not, I then go out and
> search a number of websites using a httprequest, parse out and insert
> the results into my catalog table (which has a fulltext index). Right
> after I insert the rows into the table I use a CONTAINSTABLE query to
> pull the results I just added and anything else that matches that has
> already been added to the table from previous search results.
>
> The problem is that the latest search results are not indexed fast
> enough. So when I add the latest results and run the CONTAINSTABLE
> query my latest results are not included. If I however put the thread
> to sleep for 2 seconds and then execute the query my latest additions
> do show up.
>
> My queston is, is there a way to do this without using the thread
> sleep? Is there a way to index my results instantly and making them
> available without using a 2 second pause? Has anyone else had similar
> problems?
>
> Any advice is highly appreciated. Thanks for your help.