Performance timing of a SQL report often showed wrong information¶

What is new - 24.0¶

The Performance timing list in the Performance Information dialog often showed an excessively high number for read records. Numbers in billion milliseconds were reported. This issue was caused by the optimization setting in a Visual 'C' project. The performance timing is now realistic. For SQL queries, the performance is now also divided into Create and Execute SQL statements.