Well, the code uses an ODBC interface to call stored procedures in SAP DB. So only the code the interfaces the database needs to be tweaked for other databases. Unfortunitely, that's the bulk of the code...
Actually, the DBT-1 kit has a mode where it fakes the database transaction part. The other two kits lack that at the moment.
Since we're using SAP DB at the OSDL for our performance work, I can't really respond to why we aren't using it. While there are some things we would like to see in SAP DB, just like most of the other open source databases, SAP DB is certainly viable for many applications. Part of our work is to exploit any weaknesses in a RDBMS Linux solution. We are focusing on SAP DB for our workload, but the project certainly isn't limited to that particular database.
Slashdot Mirror
I think it would still be worthwhile to give MySQL a shot, to see how it does. Anyone can get help from the OSDL folks from a couple of mailing lists:
f ormance@osdl.org
osdldbt-general@lists.sourceforge.net
osdl_per
And DBT-3 is mostly script based, so that should be really easy to run against other databases. It will just be a matter of SQL compatability.
Well, the code uses an ODBC interface to call stored procedures in SAP DB. So only the code the interfaces the database needs to be tweaked for other databases. Unfortunitely, that's the bulk of the code...
Actually, the DBT-1 kit has a mode where it fakes the database transaction part. The other two kits lack that at the moment.
Since we're using SAP DB at the OSDL for our performance work, I can't really respond to why we aren't using it. While there are some things we would like to see in SAP DB, just like most of the other open source databases, SAP DB is certainly viable for many applications. Part of our work is to exploit any weaknesses in a RDBMS Linux solution. We are focusing on SAP DB for our workload, but the project certainly isn't limited to that particular database.
Mark Wong