Having converted our development databases to IMAGE/SQL, we've ran a couple
of very simple comparison tests before and after IMAGE/SQL in an attempt to
quantify any overhead. We're trying to determine if and by how much our
current Transact/iX applications might "slow down" simply by adding the SQL
interface.

Looking at the CPU total, we find no increase for "read-only" jobs and an
increase of about 10% for "put-and-update" jobs.

-Are these figures about right ? Can anyone confirm ?
-Are there any known situations where we should expect an even greater
overhead ?
-Is there any remedial action to minimize the overhead ?
-Would concurrent SQL and native accessors place a higher demand on
resources, compared to an equal number of SQL only accessors ?

Thank you for your patience ... :)

Costas Anastassiades,
Intracom Sa
Athens-Greece