Re: Ignored words problem
From: Nick Gilbert (news_at_nickgilbert.com)
Date: 07/16/04
- Next message: Hilary Cotter: "Re: Full Text Help"
- Previous message: Ahsan: "RE: FULL TEXT SEARCH"
- In reply to: John Kane: "Re: Ignored words problem"
- Next in thread: Hilary Cotter: "Re: Ignored words problem"
- Reply: Hilary Cotter: "Re: Ignored words problem"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 16 Jul 2004 10:04:34 +0100
Thanks John and Hilary for your detailed replies!
How so I tell if I'm using noise.enu or noise.eng? Hopefully I'm using
noise.eng because I'm in the UK, but I didn't build the server...
Thanks,
Nick....
John Kane wrote:
> Nick,
> First of all, I agree that the "A clause of the query contained only ignored
> words" problem is frustrating error to get with fulltext searches... It's
> been a pain ever since SQL 7.0 Beta3 was shipped in 1998 and once SQL Server
> 2005 (Yukon) this error will be controllable from an sp_configure setting -
> sp_configure 'transform noise words' - so you can turn off this check in SQL
> Server 2005...
>
> However, i n SQL Server 2000, you cannot *prevent* this error, but you can
> avoid it either via removing noise words from the specific language specific
> noise.* file that you are using in your FT-enabled columns. If you are using
> a web-based client tool (IE, etc) you can use either of the attached files -
> SearchPage.htm or SearchPage.zip (a zipped version of SearchPage.htm) that
> demonstrates how to remove the noise words & single letters & single numbers
> prior to submitting the user's query input to SQL Server.
>
> Q. Is it safe to change my noise words file to be empty and force a repop?
> A. Yes. Not only safe, but recommended to remove specific noise words or
> single letters & single numbers vs. emptying the entire noise.enu
> (US_English) or noise.eng (UK_English) file and then run a Full Population
> on all of your FT Catalogs.
>
> Q. Why does the below query match the pleurals (or US spelling - plurals)
> when I'm not using FORMSOF(INFLECTIONAL,blah)?
> A. Because you're jsing FREETEXT vs. CONTAINS in your query. FREETEXT is
> more forgiving, i.e., fuzzy than CONTAINS as you would not get the same
> results CONTAINS. For example using the FT-enable table pub_info in the pubs
> database and searching on 'book' will not return rows that contain 'books':
>
> select pub_id, pr_info
> from pub_info
> where contains(*,'book')
> /* -- 'books' returns:
> pub_id pr_info
> ------ --------------------------------------------------
> 9952 This is sample text data for Scootney Books, publi
> 0736 This is sample text data for New Moon Books, publi
> (2 row(s) affected)
>
> -- 'book' returns:
> pub_id pr_info
> ------ --------------------------------------------------
> (0 row(s) affected)
> */
>
> Regards,
> John
>
>
>
> "Nick Gilbert" <news@nickgilbert.com> wrote in message
> news:OSzBuMmaEHA.2056@TK2MSFTNGP12.phx.gbl...
>> Why does the below query match the pleurals when I'm not using
>> FORMSOF(INFLECTIONAL,blah)?
>>
>> SELECT Category as CategoryName
>> FROM tblCategory
>> WHERE FREETEXT(tblCategory.*, 'studios')
>> AND FREETEXT(tblCategory.*, 'charts')
>>
>> Results:
>>
>> CategoryName
>> --------------------------------
>> Studio Chart
>> Studio Chart, Specialised Stages
>>
>>
>> I thought you had to use FORMSOF INFLECTIONAL to get it to match pleurals?
>>
>> Nick...
>
>
>
> *Search:*
>
>
- Next message: Hilary Cotter: "Re: Full Text Help"
- Previous message: Ahsan: "RE: FULL TEXT SEARCH"
- In reply to: John Kane: "Re: Ignored words problem"
- Next in thread: Hilary Cotter: "Re: Ignored words problem"
- Reply: Hilary Cotter: "Re: Ignored words problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|