March 11, 2009 at 8:23 pm
I managed to define my 1st full text search index in my db. My problem is noise words. According to the BOL they are used when defining the index. Fine. I defined my index using the language spanish in my columns. My problem is now when running a query containing a so called Noise word.
This query returns 47 rows
SELECT * FROM vwSitiosSchema2009
WHERE CONTAINS(Sd_Desc, '"diseño*" AND "web*" ', LANGUAGE 3082);
This query returns 0 row
SELECT * FROM vwSitiosSchema2009
WHERE CONTAINS(Sd_Desc, '"diseño*" AND "web*" AND "dos"', LANGUAGE 3082);
This last query contains a Noise word, dos, as define in noiseESN.txt. From what I read the search should ignore it and retrieve the same number of rows as the 1st query. What could I be doing wrong ?
Jean-Luc
www.corobori.com
March 12, 2009 at 9:23 am
Sorry I can't help you immediately but I've come across this before (using english) - a couple of years ago - I'll look at my archive stuff tonight and let you know what I find.
March 12, 2009 at 1:43 pm
OK I've found the application I was thinking of and my solution was to remove the noise words before they got to SQL
In my case the VB front-end read in the noise-words.txt file and filtered out any noise words before submitting the query to SQL server. It also displayed a friendly message to the user "The words ..blah.. ..blah.. were ignored in your search" 😉 alongside the results.
Sorry I couldn't help with an pure SQL solution.
March 12, 2009 at 2:07 pm
It sounds I'll got that way. Thanks Tom.
Jean-Luc
www.corobori.com
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply