...
- Oracle Database (versions 9i, 10g, 11g, 12c, 18c, 19c)
Note: We recommend applying available patches of Oracle client as well as Oracle ODBC driver - older versions of Oracle client/driver suffered from various errors (handle leaks, instability, etc.). - Microsoft SQL Server (versions 2000 - 2005)
- Microsoft Access (versions 2000 - XP)
- PostgreSQL (versions 9.x and above). D2000 Dbmanager supports a startup parameter /NQ to better support PostgreSQL (case sensitivity in table and column names).
Note 1: in the configuration of ODBC drivers for PostgreSQL, we recommend setting the "Level of rollback on errors" parameter to Statement (or Transaction), not to Nop. Setting Nop makes the database connection unusable after any error.
Note 2: in the ODBC driver configuration for PostgreSQL, we recommend setting the "Max Varchar" parameter to a large enough value (larger than the maximum size of VARCHAR columns), otherwise the data may be truncated during page access.
Note 3: in the configuration of ODBC drivers for PostgreSQL, we recommend leaving the "bytea as LO" parameter checked for correct work with BLOBs (DB_READ_BLOB, DB_UPDATE_BLOB). - Sybase Anywhere (versions 6 - 12)
- Informix (driver version 4.10.00.16554, check a Scrollable Cursors option on Advanced tab and set Cursor Behavior to value "1 - Preserve" on Environment tab)
- Firebird (version 2.0.4, native ODBC driver or driver from GM - Software)
Note 1: Native ODBC driver (version 2.0.0.148) doesn't enable editing in paged mode (browser in HI, actions PG*). Seemingly editing works but no data are modified in the database.
Note 2: ODBC driver from GM - Software supports editing and inserting rows in paged mode, but it displays only the first row of the table.
...
- Availability on OpenVMS and HPUX platforms.
- Possibility of page access to index-organized tables of Oracle database (IOT- index-organized tables). ODBC drivers Oracle contain an error (tested for the versions 9.02.00.00 up to 9.02.00.06), that causes application crash on the page access to IOT and therefore the ODBC version of the DBManager does not provide page access if finds out that the table is IOT.
- Less leakage of system resources: ODBC drivers for Oracle (tested for versions 9.02.00.00 up to 9.02.00.06) leak 4 handles in a connect/disconnect cycle, OCI interface leak only one :-) .. in any case, we recommend to set setting a number of prepared connections for the object of Database type larger enough in order to prevent from frequent opening and closing of the connections.
- Possibility to enable the debug information on the status of the Oracle cluster (see the parameter /DBCY).
...