results. The problem seams to be with CONTAINS(SomeField, '"C*"') and
CONTAINS(SomeField, '"D*"') (so far). So I am trying to find an
Hilary Cotter wrote:
> Did you remove d from your noise word list? If not remove it and rebuild
> your catalog.
>
> --
> 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 >
>
>
> "LeCitadin" <boucher.pierre@gmail.com> wrote in message
> news:1153936041.739327.313160@s13g2000cwa.googlegroups.com...
> > Hi,
> >
> > I am experiencing a strange behavior in a full text search using the
> > CONTAINS predicate.
> >
> > SELECT SomeField
> > FROM SomeTable
> > WHERE CONTAINS(SomeField, 'D-2001-286')
> >
> > The result is
> > SomeField
> > ----------------
> > D-2001-286
> > D-2002-286
> >
> > The only explanation that could make some sense regarding the second
> > line in the result is the precense of the dash (-) caracter. I did not
> > found any information regarding this caracter in a CONTAINS expression.
> >
> > By trial an error, I found that the following query returns a list of
> > values that does not correspond to the value sought.
> >
> > SELECT SomeField
> > FROM SomeTable
> > WHERE CONTAINS(SomeField, '"D*"')
> >
> > The result is
> > SomeField
> > ----------------
> > 02-00005-8601
> > 134500-04-0003
> > 88-03-27
> >
> > and so on.
> >
> > Any ideas why this is appening ?
> >
> > Thanks in advance
> >
> > Pierre Boucher
> >