Subject Re: ORDER BY on large VARCHAR columns
Author robert_difalco
--- In, "Ann W. Harrison"
<aharrison@i...> wrote:
> First...skip is about the worst thing you can possibly do,
> since it evaluates the whole record set every time. Yo

Yep, that was pretty apparent.

> How often do you insert new data or update the long field on
> existing records?

I don't mind taking a hit on insert. They are inserted much less
frequently than they are read and they are NEVER updated. What do
you have in mind? Just beware that this is only one of the columns
we sort on. Consider a graphical paged table of these things and
that the user can click on any column to order them. I can disable
the column sortability on some fields, but not on this large one and
not on all BUT this large one.