search error

[sourceuno]

What's causing the following error after I perform a search query?

Not enough space on page (32) in index (temp RAM DBF) in the function additem

Here's my query:

select 'http://'+Url Url, Title, SiteURL,LinkToSite,HotLink,LastPost,Replies,id, Active,$$$$rank Rank from tech where Title\Body likep $$q order by LastPost

The search works fine when I remove the order by clause.

[John]

What type is LastPost? That might happen if you were ordering by a very long field.

[sourceuno]

LastPost is a date field. The strange thing is that it was working fine until I restructred the table to remove some fields by recreating the table and inserting into the new table the records without the eliminated fields.

[John]

Did you create the same indexes again? For that sort of query you should have an index such as:

create metamorph inverted index tech_ndx on tech(Title\Body, LastPost);

which will let it do the LIKEP and the ORDER BY with a single index. Note that usually it doesn't make sense to order the results of LIKEP.

[sourceuno]

I did create the same metamorph index as you mentioned. So if I do order the results, should I eliminate the rank and likep from my query? After trying this, I still get the same error.

[John]

It looks as if this might require some more information. Can you open at ticket at http://www.thunderstone.com/texis/site/ ... pport.html and include the output of tsql -V with that query, and also of

"select * from SYSCOLUMNS where TBNAME = 'tech'"

Thanks

[sourceuno]

I think I may have discovered the root of the problem. When I eliminated some fields from the table, I also changed the field length of some fields including SiteURL which was included in the metamorph inverted index. When I shortened that field from a varchar of 200 to a varchar of 80, the query worked. Is there a workaround to include this field in the index as a varchar of 200?

[John]

What is you create index statement? Were you including it as a compound field, or as part of the text to search?

[sourceuno]

I'm creating it as a compound field:

create metamorph inverted index xtechbod on tech(Title\Body,LastPost,Replies,SiteURL)

I include the last 3 fields since I have those fields as sort options.

[John]

You should not be including such large fields as compound data in the index, as it will always store as many characters as the field is defined, and with that much data you have negated a lot of the benefit of the index by making it MUCH larger.