How large is your full-text indexed table? There appears to be some
anomalies with certain words when your catalog gets very large. Bouncing
MSFTESQL can help.
--
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 [quoted text, click to view] "Nick Gilbert" <nickg@newsgroup.nospam> wrote in message
news:OmQWh4tlGHA.4220@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> I have the problem that if I search for certain phrases in SQL 2005 such
> as "voice over", it returns no results.
>
> I am using the following syntax:
>
> declare @criteria varchar(100)
> select @Criteria = N'("voice*") AND ("over*")'
>
> SELECT CategoryID, category, keywords
> FROM tblCategory
> WHERE CONTAINS(tblCategory.*, @Criteria)
>
> In SQL 2000, I fixed this by following Hillary Cotter's advice and removed
> the word "over" (and others) from the noise.eng file.
>
> However now that I'm using SQL 2005, this doesn't seem to work.
>
> I've edited both noise.eng and noise.enu, restarted the MS Search service
> AND rerun the full text population and it's still not finding the
> categories which contain the phrase "voice over".
>
> Do things work differently in SQL Server 2005 or have I missed a step?
>
> Thanks,
>
> Nick...
>
>