Re: Ignored words error strangeness

Matt,
Yes, I do... 2057 is the LCID for "British English" (or UK English) while
1033 is the LCID for "English" (or US English). Yes, the noise word files
are identical, but are linked to different "Language for Word Breaker" when
you select the column level wordbreaker... The UK English noise word file is
noise.eng, while the US English noise word file is noise.enu. If you want
the same results, which every table is giving you the error, drop the FT
Catalog and run a Full Population and re-test your query.

Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/


"Matt Jensen" <replytonewsgroups@xxxxxxxxxxxxx> wrote in message
news:uO1PQ4YJGHA.528@xxxxxxxxxxxxxxxxxxxxxxx
> Howdy
>
> I've got 2 databases on the same SQL server with full text indexes on the
> columns of tables, and one when I do a full text search on with a noise
> word eg 'a' it returns results with a in it, and the other one gives the
> 'ignored words' error.
>
> When I do sp_help_fulltext_columns on the two tables, one gives 2057, one
> gives 1033, however the noise.eng and noise.enu appear to be identical on
> the server.
>
> Anyone got any ideas what the difference may be, I just want to turn this
> feature off really?
>
> Cheers
> Matt
>
>


.

Relevant Pages

  • Re: Contains
    ... alphabet string from the noise word file repopulated the full text ... Make sure you cleared the correct noise file. ... they're in a different location to SQL Server 2000, ... English, ...
    (microsoft.public.sqlserver.fulltext)
  • Re: KB889708
    ... > My environment is active/passive, but my question is not it. ... because the gatherer process uses the noise word file too. ... When SQL Server 2000 is installed in a cluster". ...
    (microsoft.public.sqlserver.fulltext)
Loading