Subject | Timestamp index? |
---|---|
Author | hay77772000 |
Post date | 2006-10-26T01:31:06Z |
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.
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?
It also has an id which is a foreign key to another table. We will
therefore have 3 indexes on the table. Will that be a problem
performance-wise when we write to it (many times a second)?
Many thanks,
David
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.
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?
It also has an id which is a foreign key to another table. We will
therefore have 3 indexes on the table. Will that be a problem
performance-wise when we write to it (many times a second)?
Many thanks,
David