Re: Ignored words error strangeness

What noise word lists are you looking at? For SQL 2000 you should be looking
at the ones in C:\Program Files\Microsoft SQL
Server\MSSQL$instanceName\FTDATA\SQLServer$instanceName\Config

or

C:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQLServer\Config

For SQL 2005 you should be looking at C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\FTData

Note that the International English (English_UK - LCID 2057) and the
American English (English_US - LCID 1033) use the same word breakers in SQL
2000 - they implement different stemmers. In SQL 2005 they use different
word breakers and stemmers.

The problem you are encountering is with the stemmers.

One of the reasons you might be getting this error is if you have deleted
the contents of your noise word list. You should enter an single space if
you want to delete the contents.
--
Hilary Cotter
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

"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: Ignored words error strangeness
    ... For SQL 2000 you should be ... > The problem you are encountering is with the stemmers. ... > the contents of your noise word list. ... > Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Msg 7619 error
    ... locate your noise word lists and replace them with a single file. ... For SQL ... Director of Text Mining and Database Strategy ... RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
Loading