Re: containstable noise words
- From: "geek-y-guy" <noone@xxxxxxxxxxx>
- Date: Wed, 6 Sep 2006 12:06:00 -0400
Did you remove the M from your noise word lists and rebuild the catalog?
You will need to stop MSSearch/MSFTEsql when making this change.
Hi Hilary: I wanted to make sure that this was advisable and/or the best way
to handle it. I'll give that a shot.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"geek-y-guy" <noone@xxxxxxxxxxx> wrote in message
news:%231CKLmD0GHA.4816@xxxxxxxxxxxxxxxxxxxxxxx
If I use a containstable query against a word like "M&M" I get a response
Informational: The full-text search condition contained noise word(s).
(0 row(s) affected)
Even though there are many rows with "M&M" in them.
How can I get around this?
.
- References:
- containstable noise words
- From: geek-y-guy
- Re: containstable noise words
- From: Hilary Cotter
- containstable noise words
- Prev by Date: Re: how to make fuzzy search on ntext field
- Next by Date: Re: What characters are considered as word boudaries
- Previous by thread: Re: containstable noise words
- Next by thread: weighting different fields in FTcatalog?
- Index(es):
Relevant Pages
|
Loading
