Re: Won't ignore noise words, even after editing noise.enu -- HELP!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



The English stop words are in all noise word lists, even Chinese. eng is uk
English which corresponds to a lcid of 1036, US English has the noise word
list of noise.us and the lcid is 1033.

What do you get when you query select @@language and sp_configure 'default
full-text language'

The place to find the pertinent noise words for SQL Server 2005 is

C:\Program Files\Microsoft SQL Server\MSSQL.X\MSSQL\FTData where x is your
instance number

For sql 2000 its in

c:\Program Files\Microsoft SQL Server\mssql\ftdata\sqlserver\config

or

c:\Program Files\Microsoft SQL
Server\mssql$InstanceName\ftdata\sqlserver$InstanceName\config

--
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



<markdavies2003@xxxxxxx> wrote in message
news:1168471792.985421.150240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm trying to get SQL Server to ignore the noise words for the
Full-Text indexed content in a given column. I've edited the noise.eng
and noise.enu files in the c:\winnt\system32 directory so they only
have one word: qxqxqxq. So any other words will not be ignore and will
get get indexed, right?

But it's not working. After dropping the existing FT index, editing the
noise file, re-starting the SQL Server Full-Text and SQL Server
services, and then creating a new FT index, it still ignores what it
thinks are noise words. For example, I search for "as far as":
CONTAINS (colName, '"as far as"'))
but it finds all rows with "far", whether or not they have "as far as"
-- it just ignores "as", since it still considers this a noise word.

I've also tried changing the default FT Index langauge to something
besides English, like Chinese -- thinking that "as" probably isn't a
Chinese noise word (Server / Properties / Advanced / Default Full-Text
Language; changing 1033 to 1028). But same problem, even after starting
and re-starting services, etc etc.

I've spent four hours on this now, and no luck. Any suggestions? Thanks
in advance.

Mark D.



.



Relevant Pages

  • Re: noise words, @@ERROR, and stop and resume indexing
    ... @@error was fixed in SQL Server 2000 SP1. ... if this query causes an ignored-word error ... the noise word would be truly ignored. ... > Could you re-post your SQL script with the cursor code? ...
    (microsoft.public.sqlserver.fulltext)
  • Re: request for sample program for fulltext search
    ... May i know what different between CONTAINS and FREETEXT? ... US_English noise word file noise.enu that is located under ... out via pre-processing before passing it to a SQL Server contains query. ... May i enter noisy word in the search? ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Problem searching for words with "&" in them
    ... experiencing is the OS platform that you have SQL Server installed on. ... > But B&O seems to be treated as an expression rather than just a string. ... >> Edit your language specific noise word list. ... >> with BANDO, and another with the original content in. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: periods in full text
    ... Strange that I can query on 12.XT.1234 and it returns ... Is this just how SQL Server works? ... that appears to honor the punctuation is simply an artifact of the data ... word file says that 1 is a noise word. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Full-text catalog is not building properly (completely)
    ... The platform is Windows Server 2003 Standard x64 Edition with SQL Server ... > Your noise word list should contain a single space. ... >> discovered that the query was failing to return an expected result. ... coming off a fresh rebuild of the catalog (and then waiting until the ...
    (microsoft.public.sqlserver.fulltext)