Psst! Did you know DevelopmentNow is a mobile web site design agency?

Contact us for help mobilizing your site, or to sign up for our beta Mobile Web SDK!
all groups > sql server full text search > october 2007 >

sql server full text search : Re: FULL TEXT SEARCH - PROBLEM


Daniel Crichton
10/31/2007 5:30:26 PM
in wrote on Wed, 31 Oct 2007 17:11:39 +0200:

[quoted text, click to view]

Why are you using *? It doesn't work like that - FTS breaks up the indexed
columns into words, you can use a * at the end of a term for searching for
words starting with the term but it's ignored for the start. Also some
characters are ignored, so the hyphen is probably unnecessary too. This is
basically turned into

CONTAINS(Urun_Ad,'"mta1000*"')

and could also be written as

CONTAINS(Urun_Ad,'"mta1000"')

and it would still find the same row(s).


[quoted text, click to view]

What is the actual CONTAINS clause you are using? If it's

CONTAINS(Urun_Ad,'"mta1000-1"')

then if the 1 is not indexed (as it's in the noise word file by default),
then it won't find that "phrase" because the 1 isn't indexed. "mta1000-1" is
the same as looking for "mta1000 1", and if the 1 isn't indexed then the
phrase won't be found.

What is in your noise words list?


Dan

Hilary Cotter
10/31/2007 7:25:21 PM
Is 1 in your noise word list?

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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
[quoted text, click to view]

AddThis Social Bookmark Button