Are there any results that actually have those 3 words near each other ?
Russ
-Original Message-
From: Matt Quackenbush [mailto:quackfu...@gmail.com]
Sent: 23 November 2010 18:01
To: cf-talk
Subject: (ot) SQL Server Full-Text Search CONTAINS()
SQL Server 2005
For the life of me, I
Ayep. The band name is My Chemical Romance. I'd say that definitely
qualifies as NEAR. :-)
~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
I'm not overly familiar with NEAR but most of the examples I've seen where
NEAR is strung together show it without the quotes.
CONTAINS (EventName,'my NEAR chemical NEAR romance')
That's probably no help, but I thought I'd share.
On Tue, Nov 23, 2010 at 1:00 PM, Matt Quackenbush
@ Michael-
Unfortunately, you are correct: That's no help. Same result without the
quotes. :-(
I know that noise words are ignored, but what appears to be happening is
that it is ignoring the entire thing, rather than just the (possible) noise
word my.
: (ot) SQL Server Full-Text Search CONTAINS()
I'm not overly familiar with NEAR but most of the examples I've seen where
NEAR is strung together show it without the quotes.
CONTAINS (EventName,'my NEAR chemical NEAR romance')
That's probably no help, but I thought I'd share.
On Tue, Nov 23, 2010
Thanks for the tip on using just a single NEAR keyword. In this particular
example (my chemical romance), it still results in no records being
returned. The only thing I can figure is that 'my' is a noise word, and all
searching is ignored once a noise word is hit.
For the time being, I've
Matt,
I googled on sql server noise words and found this link:
http://arcanecode.com/2008/05/29/creating-and-customizing-noise-words-in-sql-server-2005-full-text-search/
I followed the directions and found the noise lookup file being used by SQL
Server 2005 on my computer, and confirmed that
Carl,
Thanks for that link. I appreciate it. :-)
I guess I am simply totally misunderstanding noise/stop words in SQL
Server. My understanding was that they were ignored in a query. But the
behavior I am seeing indicates that the entire search string is ignored if
such a word is
I now recall having this issue myself many years ago, and the reason it
doesn't work is because the noise words (now called stop words) are not
actually indexed, rather than being stripped from the search which is what
you assumed. On SQL 2000 you couldn't even use the stop words period or you
Just an off-the-wall idea.
Did you try a different order to the words? I.E. chemical NEAR romance
AND my
I was speculating what might happen of the 'noise' word came later in
the list.
~|
Order the Adobe Coldfusion
@ Russ-
Thanks for the reply. I've read that page so many times that it's all just
gibberish right now. My brain is mush. LOL
Suffice it to say, as you stated, when encountered in a FTS search string,
noise/stop words block any results from being delivered.
@ Ian-
I had not tried that
-
From: Matt Quackenbush [mailto:quackfu...@gmail.com]
Sent: 23 November 2010 22:07
To: cf-talk
Subject: Re: (ot) SQL Server Full-Text Search CONTAINS()
@ Russ-
Thanks for the reply. I've read that page so many times that it's all just
gibberish right now. My brain is mush. LOL
Suffice
Russ,
You did, of course, state why, but it did not click until you just reworded
it. Thank you! It makes perfect sense now.
(And yes, I had already changed to removing noise words from the search
string.)
~|
Order the
13 matches
Mail list logo
