...
- Oracle Database (versions 9i, 10g, 11g, 12c, 18c, 19c)
Note: We recommend applying available patches of the Oracle client as well as the Oracle ODBC driver - older versions of the Oracle client/driver suffered from various errors (handle leaks, instability, etc.). - Microsoft SQL Server (versions 2000 - 2005)
Note: in a specific situation, the UPDATE trigger was able to affect the DB(S)_UPDATE action, so that it failed because the ODBC function SQLRowCount returned 0 (even though the data was updated). This case can be diagnosed by turning on the debugging category RTM.DBMANAGER.UPDATE.MSSQL.0 (if the category is active, it is ignored that SQLRowCount returns 0 changed rows). - Microsoft Access (versions 2000 - XP)
- PostgreSQL (versions 9.x and above). D2000 Dbmanager supports the /NQ startup parameter 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. The Nop setting makes the database connection unusable after any error. The Transaction setting will cause some actions to behave non-standardly (e.g. a DB(S)_INSUPD action inserting several rows will not insert anything if an error occurs while inserting any of the rows).
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. Similarly, we recommend setting the "Max LongVarchar" parameter to a sufficiently large value (larger than the maximum VARCHAR data size used in columns whose size is not explicitly specified). On the Linux platform, the parameters in odbc.ini are called MaxVarcharSize and MaxLongVarcharSize (they are also called the same in the Windows registry).
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 the Scrollable Cursors option on the Advanced tab and set Cursor Behavior to value "1 - Preserve" on the 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 is 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 HP-UX platforms.
- Possibility of page access to index-organized tables of the Oracle database (IOT- index-organized tables). ODBC drivers Oracle contain an error (tested for versions 9.02.00.00 up to 9.02.00.06), that causes an application crash on the page access to IOT and therefore the ODBC version of the DBManager does not provide page access if it 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 leaks only one :-) .. in any case, we recommend setting a number of prepared connections for the object of Database type larger enough in order to prevent frequent opening and closing of the connections.
- Possibility to enable the debug information on the status of the Oracle cluster (see the parameter /DBCY).
...