Home/ Questions/Q 3492782
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T11:48:04+00:00

I’m experimenting with full text search. I have a 50 million row table with

  • 0

I’m experimenting with full text search. I have a 50 million row table with an xml field, and set up a full text search on it. It’s 2 days later now, and the indexing is STILL ONGOING. It looks like it’s not completely hung, and is continuing to index, but very, very slowly. I based this on the fact that when I query the table, i get more results all the time. Also, looking at the full text index properties (right-click on table in sql server management studio) the Full Text Docs Processed continues to go up

Is this normal, for indxing to be so slow? At this speed, it’s not usable. I see no errors in the full text search log file. Looking at the log file more carefully – I see that apparently when I created a half million row table and put the full text index on that, it took about 1 hour to index. So, extrapolating from that, it WOULD take about 100 hours to index my table.

How can I speed this up?

thanks for any input!
Sylvia

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    With 50 million rows, you are reaching a scale where the sql servers have too much other overhead and would be better with an existing text search engine that uses inverted indexes. There are various flavors of Sharepoint search for very little money, or you could use an open source search engine and move on from there.

    • 0