Does anyone have a list of all punctuation marks ignored by the full-text
indexing service by default. Noise files (i.e. noise.dat) only explicitly
list the dollar sign ($) and the underscore (_) as noise "words".
And another observation - the Windows implementation of MS Search (compared
to the MS SQL Server implementation) yields different results - try searching
for files with the "|" character in the file name. Ok, it's an illegal
character, but the result is at least 'interesting'.
As far as the rest of the characters ignored in SQL FTS are concerned, they
don't bother Windows search. Has anyone else come across these (or other)
discrepancies?
ML
I take it you are only talking about SQL FTS, you mention Indexing Services
and MSSearch in here which are two separate products although SQL FTS uses
the MSSearch engine.
SQL FTS indexes alphanumeric characters. Most other characters are not
indexed but the engine is aware that something existed there. So a search on
AT&T will match with AT&T, AT!T, AT*T, AT$T, and AT T, if A, T, and At are
not in your noise word list.
..,!:; are discarded.
"ML" <ML@.discussions.microsoft.com> wrote in message
news:F406D8AB-E6AA-4C21-BF8E-51010B809459@.microsoft.com...
> Does anyone have a list of all punctuation marks ignored by the full-text
> indexing service by default. Noise files (i.e. noise.dat) only explicitly
> list the dollar sign ($) and the underscore (_) as noise "words".
> And another observation - the Windows implementation of MS Search
> (compared
> to the MS SQL Server implementation) yields different results - try
> searching
> for files with the "|" character in the file name. Ok, it's an illegal
> character, but the result is at least 'interesting'.
> As far as the rest of the characters ignored in SQL FTS are concerned,
> they
> don't bother Windows search. Has anyone else come across these (or other)
> discrepancies?
>
> ML
|||Thank you, very much. Yes, mainly I'm referring to SQL FTS and I'm aware of
the fact tha SQL FTS and Windows Indexing Services two are separate products.
I'm just baffled by the fact that the two implementations of the MSSearch
engines differ in such a way. Any idea why?
Thanks for the list as well.
ML
No comments:
Post a Comment