Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread Hopes for ElevateDb
Thu, Aug 31 2006 12:51 PMPermanent Link

Sam
I'm hoping your next database will handle large tables (50 million rows
or larger) so that indexes can be rebuilt much much faster. (I was going
to add another "much" but didn't want to get carried awaySmiley.

Batch index updates would be a welcomed addition. Before you release
ElevateDb, try adding 50 million rows to a table with several indexes to
see how fast it is at adding the rows and maintaining the index. That's
the only feature I'd really like to see in ElevateDb.

Sam
Thu, Aug 31 2006 6:02 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Sam,

<< I'm hoping your next database will handle large tables (50 million rows
or larger) so that indexes can be rebuilt much much faster. (I was going to
add another "much" but didn't want to get carried awaySmiley.

Batch index updates would be a welcomed addition. Before you release
ElevateDb, try adding 50 million rows to a table with several indexes to
see how fast it is at adding the rows and maintaining the index. That's the
only feature I'd really like to see in ElevateDb. >>

Well, there's a trade-off between having indexes and lots of rows.
Sometimes having lots of rows means using less indexes on the table.  In
addition, ElevateDB still uses index statistics in order to allow for
accurate sequence numbers with ranges, etc., and that's the main issue why
index updates get slower when you get above 5 million records.  We could
dump the index statistics, but it would mean a lot of very unhappy campers
coming from DBISAM, and it already is a big enough conversion as it is.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image