Full Text Index hanging status=runnable waittype=NETWORKIO

I have a database with 5 tables, each with full text index. 4 of them build
just fine, the 5th, has 10 million rows. The Full Text index never seems to
finish on that one. I've let it run for as long as 36 hours and it never
finishes. When I look in the Management panel, under process info. It tells
me my status is runnable, and waittype is NETWORKIO. I've checked it over
and over and it always is in this state. The MSSEARCH task is running with a
very high % of CPU. Any advice on where I can go from here to figure out
what the problem is?
Brian,
Try running a DBCC CHECKTABLE on the table.
HTH
Jerry
"Brian Kitt" <BrianKitt@.discussions.microsoft.com> wrote in message
news:0CD8143A-1D89-496E-BCA7-EE772790D532@.microsoft.com...
>I have a database with 5 tables, each with full text index. 4 of them
>build
> just fine, the 5th, has 10 million rows. The Full Text index never seems
> to
> finish on that one. I've let it run for as long as 36 hours and it never
> finishes. When I look in the Management panel, under process info. It
> tells
> me my status is runnable, and waittype is NETWORKIO. I've checked it over
> and over and it always is in this state. The MSSEARCH task is running
> with a
> very high % of CPU. Any advice on where I can go from here to figure out
> what the problem is?
|||I figured it out!!!!!!!!!!!!!!!
I looked at the data, and 1 column that I was indexing on, had one word, the
word 'book' for about 7,000,000 rows! I stopped indexing on that column, and
it works fine now!
"Brian Kitt" wrote:

> I have a database with 5 tables, each with full text index. 4 of them build
> just fine, the 5th, has 10 million rows. The Full Text index never seems to
> finish on that one. I've let it run for as long as 36 hours and it never
> finishes. When I look in the Management panel, under process info. It tells
> me my status is runnable, and waittype is NETWORKIO. I've checked it over
> and over and it always is in this state. The MSSEARCH task is running with a
> very high % of CPU. Any advice on where I can go from here to figure out
> what the problem is?