Cannot search FTI on certain common words (the, like, and, to, etc.)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mago - 09 Apr 2008 09:07 GMT

As the title says, I'm having problems returning results when the
search string contains any of the words in the list in the title.

I'm damned if I can work out why this is happening, as my noise words
file is empty, and anyway, the search returns no results, even if
there are other words in search string - e.g. CONTAINS(l3_Title,
'"like father"), or CONTAINS(l3_Title, '"like" AND "father"').

I've also rebuilt the catalog, with no success.

If anyone knows why this is happening, I'd be grateful for an answer.

Reply to this Message

Russell Fields - 09 Apr 2008 14:51 GMT

Mago,

How empty is your noise word file? If it is completely empty (0 length) I
believe that the default noise word list will be used. You can put a single
blank in the noise word file or (as I do) one word such as
'ThisNoiseWordListIsEffectivelyEmpty'.

FWIW,
RLF

> As the title says, I'm having problems returning results when the
> search string contains any of the words in the list in the title.
[quoted text clipped - 7 lines]
>
> If anyone knows why this is happening, I'd be grateful for an answer.

Reply to this Message

Hilary Cotter - 10 Apr 2008 00:26 GMT

The most common reason for this is editing the incorrect noise word list.
For US English, edit noise.enu (SQL Server 2000) for UK/International
English, edit noise.eng. In SQL 2005 edit noiseenu.txt and noiseeng.txt.

Note as you appear to be Italian you should edit noise.ita or noiseita.txt
for SQL 2000 and 2005 respectively.

These files can be found in C:\Program Files\Microsoft SQL
Server\MSSQL.X\MSSQL\FTData where X is your instance number in SQL 2005, and
in C:\Program Files\Microsoft SQL
Server\MSSQL$InstanceName\FTDATA\SQLServer$InstanceName\Config in SQL 2000.

Signature

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

Reply to this Message

Mago - 10 Apr 2008 11:42 GMT

> The most common reason for this is editing the incorrect noise word list.
> For US English, edit noise.enu (SQL Server 2000) for UK/International
[quoted text clipped - 25 lines]
>
> > If anyone knows why this is happening, I'd be grateful for an answer.

Thanks for the replies - I was looking in the wrong installation path
for the FTI noisewords files. Clearing the correct ones seems to have
sorted the issue.

Thanks again.

Reply to this Message