Too many full-text columns or the full-text query is too c..

FAQ

Profile

Too many full-text columns or the full-text query is too c..

Database Forums (Home) -> Full Text

Next: check pending state

Author

Message

OLAPFOREVER

External

Since: May 25, 2007
Posts: 8

(Msg. 1) Posted: Fri Jul 06, 2007 7:16 am Post subject: Too many full-text columns or the full-text query is too complex Archived from groups: microsoft>public>sqlserver>fulltext (more info?)

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 ? >> Stay informed about: Too many full-text columns or the full-text query is too c..

OLAPFOREVER

External

Since: May 25, 2007
Posts: 8

(Msg. 2) Posted: Fri Jul 06, 2007 7:18 am Post subject: RE: Too many full-text columns or the full-text query is too complex [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

Im run under SQL Server 2005 sp2 "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 ? > >> Stay informed about: Too many full-text columns or the full-text query is too c..

Mohit K. Gupta

External

Since: Jun 29, 2007
Posts: 35

(Msg. 3) Posted: Fri Jul 06, 2007 10:58 am Post subject: RE: Too many full-text columns or the full-text query is too complex [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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 ? > >> Stay informed about: Too many full-text columns or the full-text query is too c..

OLAPFOREVER

External

Since: May 25, 2007
Posts: 8

(Msg. 4) Posted: Fri Jul 06, 2007 11:04 am Post subject: RE: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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 ? > > >> Stay informed about: Too many full-text columns or the full-text query is too c..

Mohit K. Gupta

External

Since: Jun 29, 2007
Posts: 35

(Msg. 5) Posted: Fri Jul 06, 2007 11:28 am Post subject: RE: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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 ? > > > >> Stay informed about: Too many full-text columns or the full-text query is too c..

OLAPFOREVER

External

Since: May 25, 2007
Posts: 8

(Msg. 6) Posted: Fri Jul 06, 2007 12:18 pm Post subject: RE: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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 ? > > > > >> Stay informed about: Too many full-text columns or the full-text query is too c..

Mohit K. Gupta

External

Since: Jun 29, 2007
Posts: 35

(Msg. 7) Posted: Fri Jul 06, 2007 12:38 pm Post subject: RE: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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 >> Stay informed about: Too many full-text columns or the full-text query is too c..

Hilary Cotter3

External

Since: Aug 28, 2004
Posts: 1259

(Msg. 8) Posted: Mon Jul 09, 2007 8:52 am Post subject: Re: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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" wrote in message > 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 ? >> > > > >> Stay informed about: Too many full-text columns or the full-text query is too c..

OLAPFOREVER

External

Since: May 25, 2007
Posts: 8

(Msg. 9) Posted: Mon Jul 09, 2007 8:52 am Post subject: Re: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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" wrote in message > > > 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 ? > >> > > > > > > >> Stay informed about: Too many full-text columns or the full-text query is too c..

OLAPFOREVER

External

Since: May 25, 2007
Posts: 8

(Msg. 10) Posted: Tue Jul 10, 2007 9:50 am Post subject: Re: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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" wrote in message > > > > > 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 ? > > >> > > > > > > > > > >> Stay informed about: Too many full-text columns or the full-text query is too c..

Hilary Cotter3

External

Since: Aug 28, 2004
Posts: 1259

(Msg. 11) Posted: Mon Jul 16, 2007 1:04 pm Post subject: Re: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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" wrote in message > 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" wrote in message >> > >> > > 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 ? >> > >> > > > >> > >> > >> > >> Stay informed about: Too many full-text columns or the full-text query is too c..

OLAPFOREVER

External

Since: May 25, 2007
Posts: 8

(Msg. 12) Posted: Mon Jul 16, 2007 1:04 pm Post subject: Re: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

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" wrote in message > > > 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" wrote in message > >> > > >> > > 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 ? > >> > >> > > > > >> > > >> > > >> > > > > >> Stay informed about: Too many full-text columns or the full-text query is too c..

External

Since: Jun 18, 2007
Posts: 9

(Msg. 13) Posted: Tue Aug 07, 2007 3:24 pm Post subject: Re: Too many full-text columns or the full-text query is too compl [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

On 16 Jul., 19:16, OLAPFOREVER 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 > > "OLAPFOREVER" wrote in message > > > > > 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" wrote in message > > >> > > > >> > > 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 Msg9937Error 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: > > > >> > >> > > > Msg9937, 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 ?- Zitierten Text ausblenden - > > - 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 >> Stay informed about: Too many full-text columns or the full-text query is too c..

Svend Tang

External

Since: Oct 01, 2010
Posts: 1

Display posts from previous:

Related Topics:

Full Text Search on varbinary columns - Hi, I have installed SQL Server 2005 Express Edition with Advanced Services and I tried to process a full-text search on a varbinary or image column. I insert in this column ppt-files. But it returns always 0 rows, although I searched some words that are...

querying columns - 2005 full text catalog - Hello,I have been trying some methods of querying different columns using a 2005 full text catalog.http://technet.microsoft.com/en-gb/library/ms345119.aspx#yukonftsea_topic5e.g.1 SELECT pk, txtCol2, txtCol3 FROM myFt_Table WHERE CONTAINS( ( txtCol2,..

Multiple columns full text search doesn't seems to work pr.. - Hi all ! I have a full text search index on a table with several fields indexed. I tried the following query : SELECT MyIndexedTable.MyIndexedTableID MyIndexedTable.Title, KEY_TBL.RANK RANK_Total FROM MyIndexedTable INNER JOIN..

Ignored words in the full text query - Got a bizarre problem In our search box, someone types in the search term: A$ This results in the PARTIAL SQL: ......AND (CONTAINS(TableToQuery, ' ""A$"" ')) And this results in the error: Server: Msg 7619, Level 16, St...

Full text query contained only ignored words - Hello All, Please explain this Fulltext behavior to me. We have an asp application that is using sql that returns the above error when you search for the word can't. If you search for "don't" or "Doesn't" or pretty much anything ...

	Database Forums (Home) -> Full Text	All times are: Pacific Time (US & Canada)
Page 1 of 1

You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum