I have installed full text searching on a table on Sql 2000 (sp4 is
installed).
It is hanging while it is indexing. I have the re-indexing set at
every 10 minutes.
Any ideas?
Thanks,
Marc
Is there a lot of activity on this table? Expect locking if the table is
heavily updated. Try to run profiler to give you hints as to what is
occurring on the table during the population. Also what sort of population
are you running? I think you will find that change tracking offers the best
performance.
Hilary Cotter
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
"Marc" <Marc@.discussions.microsoft.com> wrote in message
news:E9D4E872-A2C3-4176-9210-A0BA654A126B@.microsoft.com...
> I have installed full text searching on a table on Sql 2000 (sp4 is
> installed).
> It is hanging while it is indexing. I have the re-indexing set at
> every 10 minutes.
> Any ideas?
> Thanks,
> Marc
>
2012年3月11日星期日
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?
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?
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 tell
s
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, an
d
it works fine now!
"Brian Kitt" wrote:
> I have a database with 5 tables, each with full text index. 4 of them bui
ld
> 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 te
lls
> 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 wit
h a
> very high % of CPU. Any advice on where I can go from here to figure out
> what the problem is?
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 tell
s
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, an
d
it works fine now!
"Brian Kitt" wrote:
> I have a database with 5 tables, each with full text index. 4 of them bui
ld
> 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 te
lls
> 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 wit
h a
> very high % of CPU. Any advice on where I can go from here to figure out
> what the problem is?
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?
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?
订阅：
博文 (Atom)