All non alphanumeric characters are thrown away and replaced by white space.
So a search on A will match with a!, !a, a@, @a, a#, a$, a%, "a.", "a,",
etc. A search on a! will match with A!, a., a, a$, (A, etc. Note that its
case insensitive and this behavior applies to tokens of more than one
letter, ie !aa. Note further that a must be removed from the noise word list
for this to work.
There are some exceptions.
`,_, following any letter whether the word/letter is in the noise word list
of not will result in a new token.
So that a search on `B, or `b, will match in a case insensitive manner with
b` or `B, and the same with _. If your column has b, B, `b, and B` a search
on b, will return b and B (if they are not in the noise word list), and a
search on `b will match only with `b or `B whether b is in the noise word
list or not.
. ++ following lower cased letters, and sharp # following upper cased
letters. A search c++ will match with c++ and not with c. c does not have to
be in the noise word list for this to work. And its any letter of the
alphabet, but not numbers.
HTH - I have submitted a paper for publication on this matter to
simple-talk. It was supposed to have been published in Feb.

Signature
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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 Hilary
>
[quoted text clipped - 26 lines]
>
> Griff