Gavin Scott wrote:

> A common excuse for not doing TPC-C that I've heard is that the benchmark
> requires an SQL database.  This is clearly not the case reading the specs,
> and as far as I can tell Image has all of the database functionality
> required to implement TPC-C.

Actually it's the newer TPC-D spec which requires the use of an ANSI 92
SQL database ("or something very close to it"). Allbase/SQL might
qualify. I doubt if Image/SQL would, but I'm not a DB expert.

TPC-C and TPC-D measure different things (OLTP vs. "decision support"),
and you cannot extrapolate one benchmark from the other on any given
system, according to TPC (and common sense :). But I think Wirt's right;
TurboImage would be *great* for doing a TPC-C benchmark.

Current and past TPC benchmark descriptions and downloadable specs are
available at <http://www.tpc.org/bench.descrip.html>. It's actually
pretty interesting stuff. A couple snippets from the summary
descriptions:

"TPC-C involves a mix of five concurrent transactions of different types
and complexity either executed on-line or queued for deferred execution.
The database is comprised of nine types of records with a wide range of
record and population sizes. TPC-C is measured in transactions per
minute (tpm)."

"TPC-D represents a broad range of decision support (DS) applications
that require complex, long running queries against large complex data
structures. Real-world business questions were written against this
model, resulting in 17 complex queries."

Patrick
--
Patrick Santucci
Technical Services Systems Programmer
KVI, a division of Seabury & Smith
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If they try to rush me, I always say, 'I've only got
one other speed -- and it's slower.'"    ~ Glenn Ford