Re: Too many full-text columns or the full-text query is too compl
- From: OLAPFOREVER <OLAPFOREVER@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 Jul 2007 10:16:03 -0700
thanks for this reply but I need to use N* not Na* or Nb* etc
"Hilary Cotter" wrote:
try na* or nb* or nc*.
etc. This is not a good option for SQL FTS.
--
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
"OLAPFOREVER" <OLAPFOREVER@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9413538C-1367-4F05-92D0-85D1C9B69843@xxxxxxxxxxxxxxxx
Hi!
do you have another solution for me ?
How Can I search for N* in this case
This is a FTS bug ?
"OLAPFOREVER" wrote:
Its true Hilary
I have 3,000,000 words began by N
but How can I search for N* ?
Its a FTS bug ? a resource problem ?
"Hilary Cotter" wrote:
The problem is there are too many words beginning with n. To get
results for
such a query you should try to restrict the search somewhat, ie na*, or
nb*,
etc.
--
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
"OLAPFOREVER" <OLAPFOREVER@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:653EADB0-5A82-4342-A12D-6B6278F43114@xxxxxxxxxxxxxxxx
the problem is not de noise world list because
all other letter work well
I seach for all words begin by N
all others tests with A* B* C* ... Z* returns results or nothing
(no
row)
but N* retrurn the Msg 9937 Error message
"Mohit K. Gupta" wrote:
I am sorry. Anyhow, are you trying to find words like 'Anything' or
words
like 'Nothing'.
N* will not catch Anything because it is not a prefixed, it will
only
catch
Nothing. I couldn't get it to ignore 'Nothing'.
I highly douht it but you can check the noise world list.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"OLAPFOREVER" wrote:
select * from Table1 where contains ((Col1,Col2,Col3),'"n*"' )
Col1, Col2 , and Col3 are the Fts Indexed Columns and I search
for N*
is it must clear ?
"Mohit K. Gupta" wrote:
Hmmm is that the right query?
Doesn't look right, try:
For One search...
SELECT *
FROM Table1
WHERE CONTAINS(FTSField, ' "N*" ');
Multi-Search ...
SELECT *
FROM Table1
WHERE CONTAINS(FTSField, ' "A*" OR "N*" ');
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"OLAPFOREVER" wrote:
Msg 9937, Level 16, State 5, Line 1
Too many full-text columns or the full-text query is too
complex to
be
executed.
HI
When I search for that in FTS I got this error
select * from Table1 where contains (a,b,c),'"n*"' )
but if I seach for a*, b* or z* all its ok just n* cause
problem
I try to reorganize the catalog with alter fulltext catalog
ftcatalog
reorganize
and alter fulltext catalog ftcatalog rebuild but the
probleme
appear again
could you help me ?
- References:
- RE: Too many full-text columns or the full-text query is too compl
- From: Mohit K. Gupta
- RE: Too many full-text columns or the full-text query is too compl
- From: OLAPFOREVER
- Re: Too many full-text columns or the full-text query is too compl
- From: Hilary Cotter
- Re: Too many full-text columns or the full-text query is too compl
- From: OLAPFOREVER
- Re: Too many full-text columns or the full-text query is too compl
- From: OLAPFOREVER
- Re: Too many full-text columns or the full-text query is too compl
- From: Hilary Cotter
- RE: Too many full-text columns or the full-text query is too compl
- Prev by Date: Re: Too many full-text columns or the full-text query is too compl
- Next by Date: Re: Searching on #
- Previous by thread: Re: Too many full-text columns or the full-text query is too compl
- Next by thread: Re: Update to SP4 causes starnge Server behavior
- Index(es):
Relevant Pages
|
