Local ODBC on Linux and UNIX– The local ODBC client is now supported on Linux and UNIX platforms in both 32-bit and 64-bit. Earlier the local ODBC client was only supported on Windows.
Support for embedding the OpenAccess SDK Server – The OpenAccess SDK server can be embedded into a native or a Java process to allow the data processing to happen in the same address space as the data source.
Improved and extended branding support– Branding tools have been extended and improved to allow branding the ODBC and JDBC clients on all platforms, branding the Management Console, branding the Setup and Login dialog boxes for ODBC, and branding Interactive SQL.
ODBC client exits – The ODBC client can be configured to call a custom SQLDriverConnectW and SQLConnectW function to allow additional processing to be done on the client side before processing the connection.
Customizable run-time installers– Customizable run-time installers support the creation of run-time installers for ODBC client and OpenAccess Server on Windows. This feature allows installers to be created by editing a text file to change name of the product and other properties.
Multi-platform license keys– A single license key can enable the use of the ODBC client or the Server on every supported platform. Earlier a unique key was required for each platform.
Cursor based processing of stored procedure results– Results from a stored procedure can be returned in cursor mode. Earlier the complete results from a stored procedure were collected in memory before sending them to the client.
Cursor based processing of aggregates – Results from GROUP BY queries are sent to the client as soon as the number of groups specified by the fetch block size is collected in memory. Earlier all groups were brought into memory before sending to the client and this limited the size of the GROUP BY results that could be handled.
Configuration parameters are centralized – All configuration parameters are now stored in oadm.ini and managed using the OpenAccess SDK Manager. Earlier the configuration parameters for the OpenAccess SDK Server were stored in both the oadmi.ini file that is managed using the OpenAccess SDK Manager and in the oasql.ini file that had to be manually edited.