Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / August 2005

Tip: Looking for answers? Try searching our database.

Noise word blues

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Wayne Antinore - 31 Aug 2005 13:55 GMT
Hi,
I'm having a noise word problem that I don't seem to see in any of the other
postings.
Here is the setup:
SQL Server 2000 Standard Edition SP3 running on Win 2003 Server.
In order to avoid the normal noise word problems we edited the noise word
file for english by just putting a space in it and saving the file and
restarting SQL Server and the search service (reboot of machine actually).
However there are still some characters that when used with a CONTAINS still
give back the noise word error.  The ones we found tend to be special single
characters such as "?" or "_".
An example would be:  WHERE CONTAINS(*, '"Pick" AND "?" AND "List"')
Is there any way to get these to be ignored as well or is there a
comprehensive list of these characters so we could parse them out on in the
application code?  We've tried neutral word breaking and using FREETEXT and
that didn't work either.

 Thanks in advance for any help,
     Wayne Antinore
Hilary Cotter - 31 Aug 2005 14:46 GMT
Unfortunately what you have to do is parse your content and replace these
characters with a token, i.e. replace "?" with " QuestionMark " and then in
your queries when someone is querying on a ? expand this to a query on
QuestionMark.

You will need to replace the ? mark with a token which will not be searched
on and you will need to surround this token with white space for it to work
correctly.

When you return the data to the client make sure you replace the token back
with ?, or have non marked up content somewhere and return this content
instead.

Signature

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

> Hi,
> I'm having a noise word problem that I don't seem to see in any of the other
[quoted text clipped - 15 lines]
>   Thanks in advance for any help,
>       Wayne Antinore
Wayne Antinore - 31 Aug 2005 16:00 GMT
Thanks Hilary,
Yuck!, but thanks anyway at least now I know there isn't a quick fix that
I'm missing :)

 Wayne

> Unfortunately what you have to do is parse your content and replace these
> characters with a token, i.e. replace "?" with " QuestionMark " and then
[quoted text clipped - 38 lines]
>>   Thanks in advance for any help,
>>       Wayne Antinore
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.