Re: Some Clarifications

G. Bradley MacDonald wrote:

1. Performance of Insert statement. About 90% of what is done is
Inserts. And a lot of them! Hundreds of thousands of records in one
run. This is partially the reason I am looking to support DBs like
MSSQL - while they may not have the fastest Inserts - my customers run
them on BIG hardware and that makes a diff both in terms of speed -
but also supporting larger DBs.

For MS SQL, look at bulk insert, but that is specific to that product. For
InterBase/Firebird, you can deactivate most indexes to speed up bulk inserts
and then reactivate indexes after. In general InterBase/Firebird is
considered quite good for normal insert speed as long as you manage your
transactions correctly (which really needs to be done for any relational
database anyway).

4. The Indexes should be able to handle string fields of at least 256
in size. 512 would be preferrable. Total Index size of 600 would be
ideal.

Do you really need to index such large fields? That is definitely one area
where InterBase/Firebird won't meet your requirements, max is a little less
than 256 (232 IIRC), and that is less if using a multibyte character set.

Unless #4 is really a killer, I would still recommend InterBase/Firebird.
They meet all your other criteria well. InterBase has a desktop license
that's pretty cheap and the latest version is much faster than previous
ones.

--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: http://www.logicfundamentals.com/RADBooks.html
"Those who disdain wealth as a worthy goal for an individual or a
society seem not to realize that wealth is the only thing that can
prevent poverty." - Thomas Sowell


.