Efficient use of text-containing field

[Ruslan Zasukhin]

On 12/6/05 5:25 AM, "jda" <jda at his.com> wrote:

>> If not, then the String(16) approach is probably your best bet, because as I
>> noted you can't index a field declared as IndexByWords.  If speed is a total
>> non issue and you only needed do the sort once after filling the table and
>> then using it read-only you could certainly use the String(16) approach to
>> sort, then fill in a SortOrder field based upon the result, and then throw
>> the String(16) field away... Or build the String(16) array in a parallel
>> temporary table that you subsequently punt.
>> 
>> Hope that helps.
>> 
> 
> Thank you, but I need the VarChar to store the data (which can be
> large) and is indexed by word. That is why I need a sort method that
> is not indexed by word. My question to Ruslan is whether VarChar(16)
> saves me storage space. Ruslan?

Yes of course. 

    Index built on first 16 chars will be much less of index built on all.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]