Details

    • Type: Explanation
    • Status: Obsolete
    • Affects Version/s: EXASolution 4.2.0, EXASOL 6.0.0, Exasol 6.1.0, EXASolution 5.0.0
    • Fix Version/s: None
    • Component/s: Client SDK
    • Labels:
      None
    • Environment:
    • Explanation:
      Hide

      Note: This solution is no longer up to date. For the latest information, please refer to our documentation portal: https://docs.exasol.com/connect_exasol/drivers/sdk_cli.htm

      ---------------------------------------------------------------------------------------------------------------------------------------------

      The native interface (EXASolution CLI) implements the majority of the ODBC variation of the Call Level Interfaces Standard. The interface functions are very similar to the ODBC functions; in most cases, the only distinguishing factor is the prefix "EXA".

      Why use EXASolution CLI interface

      *EXASolution CLI is faster than ODBC and JDBC

      • Special EXASolution functionality is supported (e.g. batch execution, parallel reading, parallel insertion)
      • The EXASolution CLI Library is available for Windows and Linux
      • Every ODBC programmer will become familiar with the EXASolution CLI Interface very quickly

      Best Practice for developers

      Reading big data volumes

      When reading big data volumes, never use SQLGetData, but instead SQLBindCol and SQLFetch.To achieve the best performance you should try to fetch about 50-100 MB of data by choosing the number of rows per SQLFetch.

      Writing big data volumes

      Instead of using single insert statements like "INSERT INTO t VALUES1, 2, ...", you should use the more efficient interface of prepared statements and their parameters. Prepared statements achieve optimal performance when using parameter sets between 50 and 100 MB. Moreover you should insert the data by using the native data types. E.g. for number 1234 you should use SQL_C_SLONG (Integer) instead of SQL_CHAR ("1234").

      Show
      Note: This solution is no longer up to date. For the latest information, please refer to our documentation portal:  https://docs.exasol.com/connect_exasol/drivers/sdk_cli.htm --------------------------------------------------------------------------------------------------------------------------------------------- The native interface (EXASolution CLI) implements the majority of the ODBC variation of the Call Level Interfaces Standard. The interface functions are very similar to the ODBC functions; in most cases, the only distinguishing factor is the prefix "EXA". Why use EXASolution CLI interface *EXASolution CLI is faster than ODBC and JDBC Special EXASolution functionality is supported (e.g. batch execution, parallel reading, parallel insertion) The EXASolution CLI Library is available for Windows and Linux Every ODBC programmer will become familiar with the EXASolution CLI Interface very quickly Best Practice for developers Reading big data volumes When reading big data volumes, never use SQLGetData, but instead SQLBindCol and SQLFetch.To achieve the best performance you should try to fetch about 50-100 MB of data by choosing the number of rows per SQLFetch. Writing big data volumes Instead of using single insert statements like "INSERT INTO t VALUES1, 2, ...", you should use the more efficient interface of prepared statements and their parameters. Prepared statements achieve optimal performance when using parameter sets between 50 and 100 MB. Moreover you should insert the data by using the native data types. E.g. for number 1234 you should use SQL_C_SLONG (Integer) instead of SQL_CHAR ("1234").
    • Category 1:
      Clients, Interfaces & Drivers - Native CLI Interface

      Attachments

        Activity

          People

          • Assignee:
            CaptainEXA Captain EXASOL
            Reporter:
            CaptainEXA Captain EXASOL
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: