At 11:31 AM 26/10/2006, you wrote:

>Hi,
>
>We have a table that grows very rapidly, and can contain millions of
>records. We're trying to figure out the best indexing on it. Usually
>we will display the records in the UI based on the record's timestamp,
>in ascending or descending order.

No problem.

>Is it a problem to create 2 indexes on this field (asc and desc)? I
>seem to remember reading in the Firebird book that you shouldn't index
>timestamp fields?

No; the advice was not to use a timestamp field as a primary key
because, obviously, it has the potential to be non-unique.

./heLen