Each statement entered via ODBC causes an additional select statement which is parsed without execut
I hope that this is the correct community.
Situation:
A perfstat report shows an "exec to parse" relation of -40% (very very bad)
It is caused by select statements with the following build order : select <col1>, <col2>, .., <colx> from <tablename> without any where clause (let us call it: AllColumnSelect).
Such a statement is generated whenever an insert/update/delete/select statement is entered.
The AllColumnSelect statement is generated and parsed but never executed by the ODBC call SQLPrepare(<orig_statement>) where <orig_statement> is the original statement.
But you can use ODBC in two ways
a.) SQLPrepare() and afterwards SQLExecute()