Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2005-05-11 : 07:29:28
|
| NetWeb writes "Hello All,We are using SQL Server 2000 as our database. We have implemented full text catalog for the free text searching utility in our application. While testing the implementation of the mentioned catalog based search, we found that the search mechanism igoners '_' (underscore) when specified as the first character of search text. For example, search result for "_option" returns result for "option" and "_" is ignored when there is a valid content that has occurences of "_option" or "_new". We also believe that SQL server catalog based search does not consider "_" as either a Punctuation symbol or a Word breaker.We are not able to figure out why is the search result for "_option" is returning result for only "option" and ignoring the content "_option". We would appreciate a help on this matter.For more details on this matter, When we run any one of the following query, we get the same results.Query-1:----------SELECT *FROM searchtableWHERE CONTAINS(freetext, '"_option*"')Query-2:----------SELECT *FROM searchtableWHERE CONTAINS(freetext, '"option*"')" |
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2005-05-11 : 09:16:57
|
| By default, SQL server ignores most symbols and special characters. You can configure SQL Server to stop considering the underscore character as a "noise word" by removing it from the noise.dat file in your server's full text index configuration folder (typically C:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQLServer\Config). Scroll down to the bottom of the noise.dat file and delete the "_" character. you will have to rebuild your full-text catalogs for it to take effect.OS |
 |
|
|
|
|
|
Full text catalog : Search problem