reserved (ampersand) characters in full text queries

Much obliged if anyone could help.. We're having issues with people searching
with strings such as ["telecoms" and "at&t"] where the database refuses the
second term due to the ampersand character. We've switched to a language
neutral setting, but this doesn't seem to have helped -is there a way of
changing the operating mode of sql server so as to ignore the ampersand? Any
pointers greatly appreciated!
adrian
This works for me on Win2k and Win2003, SQL Server 2000 using the US
English word breaker.
Did by chance you remove the three words a, t, and at from your noise word
lists?
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
|||I'm guessing there's been no changes since all the language/noise files were
last modified back in 2000 -and I know the query fails using the US or the
neutral language settings for me.
This is what I'm trying:
SELECT TOP 20 Article_ID FROM TT_Articles WHERE
(CONTAINS(Body,'"at&t" AND "wireless"'))
and the result:
Server: Msg 7619, Level 16, State 1, Line 1
Execution of a full-text operation failed. A clause of the query contained
only ignored words.
which i thought related the '&' breaking the word, and leaving only ignored
'at' and 't'. Now I don't want to remove these two words from the noise list,
since then it will match for all 'at'(s) no? I need it to include the
ampersand.
I recall a colleague recently telling me microsoft had changed something in
the new version so C# could be searched similarly -is this the case?
Many thanks for taking the time to look into this -I'm stumped.
adrian
"Hilary Cotter" wrote:

> This works for me on Win2k and Win2003, SQL Server 2000 using the US
> English word breaker.
> Did by chance you remove the three words a, t, and at from your noise word
> lists?
> --
> 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
>
|||yes searches on at will return hits to at, and at&t and at!t.
What I normally recommend to customers is that the replace tokens like
at&t to attANDt in their content and then trap for people searching on
at&t and change the search to atANDt.
Then you either have to fix the content on the fly when you are returning
it to them, or have your content stored twice, once with at&t and another
time with atANDt
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
|||ok thanks. in this situation I don't think that's practical. I'm going to
have to write something to pick up special cases and write a slightly heavier
query (the joys of '%%') since our guys really want at&t to function.
I've come across some interesting threads if other people are interested
(seems to be a fairly well read on topic!):
http://www.sqlservercentral.com/foru...ssageid=117679
http://www.dbforumz.com/Full%20Text-...ict152560.html
Thanks for your ideas,
adrian
"Hilary Cotter" wrote:

> yes searches on at will return hits to at, and at&t and at!t.
> What I normally recommend to customers is that the replace tokens like
> at&t to attANDt in their content and then trap for people searching on
> at&t and change the search to atANDt.
> Then you either have to fix the content on the fly when you are returning
> it to them, or have your content stored twice, once with at&t and another
> time with atANDt
> --
> 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
>
|||the rule with c and j is that they will be indexed if they are followed by
++, or #, even if these letters are not in your noise word list.
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