Too many full-text columns or the full-text query is too complex
OLAPFOREVER
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 ?
OLAPFOREVER
Mohit K. Gupta
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
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
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.
OLAPFOREVER
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
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.
Hilary Cotter
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" <OLAPF...@discussions.microsoft.com> wrote in message
news:653EADB0-5A82-4342...@microsoft.com...
OLAPFOREVER
I have 3,000,000 words began by N
but How can I search for N* ?
Its a FTS bug ? a resource problem ?
OLAPFOREVER
do you have another solution for me ?
How Can I search for N* in this case
This is a FTS bug ?
Hilary Cotter
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" <OLAPF...@discussions.microsoft.com> wrote in message
news:9413538C-1367-4F05...@microsoft.com...
OLAPFOREVER
thanks for this reply but I need to use N* not Na* or Nb* etc
DC
wrote:
> 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
> >news:9413538C-1367-4F05...@microsoft.com...
> > > 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
> > >> >news:653EADB0-5A82-4342...@microsoft.com...
> > >> > > 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)
> > >> > >> > > > 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
>
>
> - Zitierten Text anzeigen -
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
Svend Tang
following hotfix described in KB982853.
You can then try to raise the maxrestriction node for the catalog.. i went to 400,000 and it worked like a charm.. finally....
AFTER APPLYING FIX RUN THE FOLLOWING:
===================================
The fix adds a new stored procedure called sp_fulltext_maxrestrictionnodes which will allow you to both see what is the current setting as well as to change it. Below is an example and syntax:
sp_fulltext_maxrestrictionnodes <catalog name> -- to see current configuration value. The default is 200,000
sp_fulltext_maxrestrictionnodes <catalog name>, <max nodes> --to set the value
In your case we need to double the value, so you would run the following:
sp_fulltext_maxrestrictionnodes <catalog name>, 400000
NOTE: You replace <catalog name> and <max Nodes> with the actual name and number. For example, if the catalog was Fingerhut, it would be sp_fulltext_maxrestrictionnodes Fingerhut, 400000 to change the value to 400000.
> On Friday, July 06, 2007 10:16 AM OLAPFOREVE 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 ?
>> On Friday, July 06, 2007 10:18 AM OLAPFOREVE wrote:
>> Im run under SQL Server 2005 sp2
>>
>> "OLAPFOREVER" wrote:
>>> On Friday, July 06, 2007 1:58 PM mohitkgupt 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:
>>>> On Friday, July 06, 2007 2:04 PM OLAPFOREVE 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:
>>>>> On Friday, July 06, 2007 2:28 PM mohitkgupt 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:
>>>>>> On Friday, July 06, 2007 3:18 PM OLAPFOREVE wrote:
>>>>>> 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:
>>>>>>> On Friday, July 06, 2007 3:38 PM mohitkgupt wrote:
>>>>>>> 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
>>>>>>> MCTS: SQL Server 2005
>>>>>>>> On Monday, July 09, 2007 8:52 AM 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" <OLAPF...@discussions.microsoft.com> wrote in message
>>>>>>>> news:653EADB0-5A82-4342...@microsoft.com...
>>>>>>>>> On Monday, July 09, 2007 9:14 AM OLAPFOREVE 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:
>>>>>>>>>> On Tuesday, July 10, 2007 12:50 PM OLAPFOREVE wrote:
>>>>>>>>>> Hi!
>>>>>>>>>>
>>>>>>>>>> do you have another solution for me ?
>>>>>>>>>> How Can I search for N* in this case
>>>>>>>>>> This is a FTS bug ?
>>>>>>>>>>
>>>>>>>>>> "OLAPFOREVER" wrote:
>>>>>>>>>>> On Monday, July 16, 2007 1:04 PM 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" <OLAPF...@discussions.microsoft.com> wrote in message
>>>>>>>>>>> news:9413538C-1367-4F05...@microsoft.com...
>>>>>>>>>>>> On Monday, July 16, 2007 1:16 PM OLAPFOREVE wrote:
>>>>>>>>>>>> thanks for this reply but I need to use N* not Na* or Nb* etc
>>>>>>>>>>>>
>>>>>>>>>>>> "Hilary Cotter" wrote:
>>>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>>>> JustCode Visual Studio Development Add-In by Telerik
>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/d174b33a-d86e-48e7-b381-fcd1938b6775/justcode-visual-studio-development-addin-by-telerik.aspx