KB search acting strange

Hello - I am having some weird results when searching the KB. I have a
document named: "AT&T Outage Exxon/Hamilton/Cessna"

In all of these examples I am using full text search, in all subjects.
match exact text

1. If I search for "Outage" I get the expected result - great
2. If I search for "Out" or "Out*", I get nothing - do I have to
specifically state something to get out*?
3. If I search for "AT&T", I get nothing - is the & causing an issue?
4. If I search for Hamilton, I get my expected results. Based on what
I have seen above I would think it would not find hamilton, perhaps the
/ allows me to search on hamilton?


Your assistance is appreciated
heather

ReeceWilliams
Sun Aug 13 17:39:01 CDT 2006

I haven't tried any of this, but my guess is that by default it only searches
on full words.
AT&T probably equates to AT & T - ie the & is considered a separator.
You'll probably find *Out* finds Outage - as it's not a full word.

HTH,
R.

"heather" wrote:

> Hello - I am having some weird results when searching the KB. I have a
> document named: "AT&T Outage Exxon/Hamilton/Cessna"
>
> In all of these examples I am using full text search, in all subjects.
> match exact text
>
> 1. If I search for "Outage" I get the expected result - great
> 2. If I search for "Out" or "Out*", I get nothing - do I have to
> specifically state something to get out*?
> 3. If I search for "AT&T", I get nothing - is the & causing an issue?
> 4. If I search for Hamilton, I get my expected results. Based on what
> I have seen above I would think it would not find hamilton, perhaps the
> / allows me to search on hamilton?
>
>
> Your assistance is appreciated
> heather
>
>

heather
Mon Aug 14 14:05:22 CDT 2006

Thanks Reece - but the search is not even finding "*out*" . I am
having no luck with wild card searches.


Reece Williams wrote:
> I haven't tried any of this, but my guess is that by default it only searches
> on full words.
> AT&T probably equates to AT & T - ie the & is considered a separator.
> You'll probably find *Out* finds Outage - as it's not a full word.
>
> HTH,
> R.
>
> "heather" wrote:
>
> > Hello - I am having some weird results when searching the KB. I have a
> > document named: "AT&T Outage Exxon/Hamilton/Cessna"
> >
> > In all of these examples I am using full text search, in all subjects.
> > match exact text
> >
> > 1. If I search for "Outage" I get the expected result - great
> > 2. If I search for "Out" or "Out*", I get nothing - do I have to
> > specifically state something to get out*?
> > 3. If I search for "AT&T", I get nothing - is the & causing an issue?
> > 4. If I search for Hamilton, I get my expected results. Based on what
> > I have seen above I would think it would not find hamilton, perhaps the
> > / allows me to search on hamilton?
> >
> >
> > Your assistance is appreciated
> > heather
> >
> >

ReeceWilliams
Mon Aug 14 18:26:02 CDT 2006

Did you try *out* and *Out*? - ie it may be case sensitive. The other thing
to try is % instead of *, although that's unlikely.

HTH,
R,

"heather" wrote:

> Thanks Reece - but the search is not even finding "*out*" . I am
> having no luck with wild card searches.
>
>
> Reece Williams wrote:
> > I haven't tried any of this, but my guess is that by default it only searches
> > on full words.
> > AT&T probably equates to AT & T - ie the & is considered a separator.
> > You'll probably find *Out* finds Outage - as it's not a full word.
> >
> > HTH,
> > R.
> >
> > "heather" wrote:
> >
> > > Hello - I am having some weird results when searching the KB. I have a
> > > document named: "AT&T Outage Exxon/Hamilton/Cessna"
> > >
> > > In all of these examples I am using full text search, in all subjects.
> > > match exact text
> > >
> > > 1. If I search for "Outage" I get the expected result - great
> > > 2. If I search for "Out" or "Out*", I get nothing - do I have to
> > > specifically state something to get out*?
> > > 3. If I search for "AT&T", I get nothing - is the & causing an issue?
> > > 4. If I search for Hamilton, I get my expected results. Based on what
> > > I have seen above I would think it would not find hamilton, perhaps the
> > > / allows me to search on hamilton?
> > >
> > >
> > > Your assistance is appreciated
> > > heather
> > >
> > >
>
>

heather
Tue Aug 15 15:31:30 CDT 2006

Tried it all. I can confirm that it is not case sensitive, but still
not able to search our anything close to the out, out*, out% or any
version thereof.

Michael
Tue Aug 15 15:52:54 CDT 2006

Maybe it's related to the noise word files. They are located in
C:\Inetpub\wwwroot\Help\noisewords and the English version contains "out",
"at" and any single character. If your search phrase is parsed and the noise
word file is used, then out may be removed from the query. AT&T may be split
into two words, "AT" and "T". As "AT" is "at" and therefore a noise word,
and "T" is a single character, they may also be removed.

This is just a guess.

--
Michael
http://www.stunnware.com/crm2
----------------------------------------------------------
"heather" <heather.thigpen@ihs.com> schrieb im Newsbeitrag
news:1155673890.864760.162480@m73g2000cwd.googlegroups.com...
> Tried it all. I can confirm that it is not case sensitive, but still
> not able to search our anything close to the out, out*, out% or any
> version thereof.
>

heather
Tue Aug 22 10:17:37 CDT 2006

Michael, Thanks for you input. After opening a call with MSFT - here
is what I learned. Full text search does not work on partial words.
Full text search does not like the & character and thats why it doesn't
find AT&T in my example. It finds Hamilton becuase the / character
gets changed to a space when being interpretted by the full text search
engine - therefore it looks like a stand alone word.

The solution I was given was to use advanced find when I need to do
this kind of searching. Not really an acceptable answer for my users.
I am training them to create key words and that consider this
limitation in creating KB's in the mean time.