On the issue of full-text indexing, urgent, masters.

shogun

In a certain table, select count (*) has 150,000 records, but the full-text index to view the unique key count is only about 70,000.
Using select * from tb_example where patindex ('% example%', fdTitle) can find 5 pieces of data, but searching the full-text index select * from tb_example where contains (fdTitle, '"* 例 *"') has only 2 pieces of data, and The full-text index has been completely populated, and it has also been incrementally populated. It should be that many have not been indexed. Excuse me, what is going on?
Thank you! ~~

sayiken

It does n’t feel like the index is incomplete ...

shogun

sayiken
What's going on? The number of unique keys in the indexed attribute is not 150,000

我是杀人狂

Specify the full-text catalog

我是杀人狂

Is there more than 450 bytes in the unique key?

shogun

Specify full-text catalog? How to specify?
450 bytes? Should n’t it be that long?

shogun

我是杀人狂, what happens if it exceeds 450 bytes?

lhailang

I also encountered a similar problem. I feel that the hit rate of the full-text index is really difficult to guarantee.

terrytian

There seems to be no way. The results of the full-text search are less each time. I haven't found more. Haha

vagrant

[code=SQL]While fulltextcatalogproperty('abc','populateStatus')<>0
begin

--If the full-text catalog is being filled, wait for 30 seconds and check again
waitfor delay '0:0:30'
end[/code]