Re: freetexttable bug
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Wed, 17 Oct 2007 07:27:39 -0400
duh silly me. You need to remove AT from your noise word list and then
rebuild your catalog.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:enGf5gGEIHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
I've repro'd this. It could be by design, I'll raise it internally and see
if it is a bug.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"Baldwin" <ibaldwinjr@xxxxxxxxx> wrote in message
news:1192202141.265102.33850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
We've been using the catalog as part of our search engine for a year
now. We use freetexttable to search for keywords and it is fine until
now. For some reason the 'freetexttable' is inconsistent.
I tried this query and I got a lot of rows.
select * from tb_catalog
where content like '%AT&T%'
When I try this, I dont get anything.
select * from freetexttable(tb_catalog, *, 'AT&T')
But when I try this, I got rows.
select * from freetexttable(tb_catalog, *, 'SB&C')
So I thought it is just an ampersand issue but it worked in the last
query.
Any thoughts are really appreciated.
Great Thanks,
Baldwin
MISICompany
.
- Follow-Ups:
- Re: freetexttable bug
- From: Baldwin
- Re: freetexttable bug
- References:
- freetexttable bug
- From: Baldwin
- Re: freetexttable bug
- From: Hilary Cotter
- freetexttable bug
- Prev by Date: Re: freetexttable bug
- Next by Date: Re: freetexttable bug
- Previous by thread: Re: freetexttable bug
- Next by thread: Re: freetexttable bug
- Index(es):
Relevant Pages
|
