all groups > sql server full text search > july 2007 >
You're in the

sql server full text search

group:

Too many full-text columns or the full-text query is too complex


Too many full-text columns or the full-text query is too complex OLAPFOREVER
7/6/2007 7:16:03 AM
sql server full text search:
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 ?
RE: Too many full-text columns or the full-text query is too complex OLAPFOREVER
7/6/2007 7:18:04 AM
Im run under SQL Server 2005 sp2

[quoted text, click to view]
RE: Too many full-text columns or the full-text query is too complex Mohit K. Gupta
7/6/2007 10:58:01 AM
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


[quoted text, click to view]
RE: Too many full-text columns or the full-text query is too compl OLAPFOREVER
7/6/2007 11:04:07 AM

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 ?



[quoted text, click to view]
RE: Too many full-text columns or the full-text query is too compl Mohit K. Gupta
7/6/2007 11:28:00 AM
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


[quoted text, click to view]
RE: Too many full-text columns or the full-text query is too compl OLAPFOREVER
7/6/2007 12:18:03 PM
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

[quoted text, click to view]
RE: Too many full-text columns or the full-text query is too compl Mohit K. Gupta
7/6/2007 12:38:04 PM
I am some what lost, would you mind posting the table struction, and the
index creation scripts here. I can try to help you troubleshoot from there,
in my thinking only reason you should be getting that is if you have more
then 16 columns in the full index.

Sorry haven't been much help.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
Re: Too many full-text columns or the full-text query is too compl OLAPFOREVER
7/9/2007 6:14:04 AM
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 ?

[quoted text, click to view]
Re: Too many full-text columns or the full-text query is too compl Hilary Cotter
7/9/2007 8:52:54 AM
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
[quoted text, click to view]

Re: Too many full-text columns or the full-text query is too compl OLAPFOREVER
7/10/2007 9:50:01 AM
Hi!

do you have another solution for me ?
How Can I search for N* in this case
This is a FTS bug ?

[quoted text, click to view]
Re: Too many full-text columns or the full-text query is too compl OLAPFOREVER
7/16/2007 10:16:03 AM

thanks for this reply but I need to use N* not Na* or Nb* etc

[quoted text, click to view]
Re: Too many full-text columns or the full-text query is too compl Hilary Cotter
7/16/2007 1:04:42 PM
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
[quoted text, click to view]

Re: Too many full-text columns or the full-text query is too compl DC
8/7/2007 3:24:29 PM
On 16 Jul., 19:16, OLAPFOREVER <OLAPFORE...@discussions.microsoft.com>
[quoted text, click to view]

Hi,

I have a similar problem: "CONTAINS(expression, ' "de*" ')" results in
error 9937. "de*" and some other two letter expressions do produce a
lot of hits, but how I am supposed to know that in advance?

Often searches like

CONTAINS(expression, ' "nokia*" AND "de*" ')

are being used. Fails with 9937 also, although the number of total
results would be much smaller. If I add "de" to the noise word list,
the only result is that "de" will have zero hits while "de*" still
fails with 9937. BTW: ' "nokia*" and "de" ' also results in zero hits,
which only makes sense if one ignores what the end user expects.

So the only chance I am seeing is to log the searches that fail with
9937 and manually build a list of strings that are being substracted
from the search phrase before it is being passed to the ft search.

Any better ideas would be great!

I think FT index in 2005 has still not grown up. The gatherer has
become really quick but other than that I see hardly any advances to
the 2000 version.

Regards
DC



AddThis Social Bookmark Button