Some of the databases and drivers tested with CompareData. Basic DBMS metadata support is limited to functionality available using ODBC catalog functions whereas extended DBMS metadata support adds support for additional features such as comparing triggers by accessing the DBMS information schema.
|DBMS||DBMS Ver||Driver||Driver Version||Test|
|4D||v11||4D v11 ODBC Driver||11.03.00.00|
|Adabas D||13.01||Adabas D||13.01.01.00|
|Advantage Database Server||9.1||Advantage StreamlineSQL ODBC||9.10.00.09|
|ANTs Data Server||3.6||ANTS ODBC Driver||3.00.00.00|
|Birdstep RDM Server||7.0||Birdstep ODBC for RDM Server 7.0||7.00.701.00|
|Easysoft ODBC-JDBC Gateway||1.03.00.01|
|Derby*, JavaDB||10.5.3.0||IBM DB2 ODBC DRIVER||9.01.00.356|
|Easysoft ODBC-JDBC Gateway||1.03.00.01|
|DB2 UDB*||126.96.36.1992||IBM DB2 ODBC Driver||8.01.10.812|
|DBISAM||4.24||DBISAM 4 ODBC Driver||4.24.00.01|
|EnterpriseDB*||8.1 Release 2||EnterpriseDB 8.1||8.01.04.19|
|FairCom c-treeSQL Server||V8.14||c-treeSQL ODBC Driver||8.24.05.29|
|FileMaker Pro||8||DataDirect 32-BIT SequeLink 5.4||1.15.12.00|
|HSQLDB||188.8.131.52||Easysoft ODBC-JDBC Gateway/HSQLDB JDBC driver||2.00.00.00|
|Informix IDS*||10.0||IBM Informix ODBC Driver||2.90.00.12335|
|Ingres 9.2*||9.2.0||Ingres 9.2||3.50.920.90|
|InterBase*||7.5||Firebird/InterBase(r) driver MT||2.00.00.136|
|Linter||6.0.8||Linter 6.0 Driver||3.00.61.00|
|Microsoft Access||2003||Microsoft Access Driver (*.mdb)||4.00.6200.00|
|2010||Microsoft Access Driver (*.mdb, *.accdb)||14.00.4760.1000|
|Microsoft Excel||2003||Microsoft Excel Driver (*.xls)||4.00.6200.00|
|2010||Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)||14.00.4760.1000|
|Microsoft SQL Server*||2000||SQL Server||2000.85.1132.00|
|2005||SQL Native Client||2005.90.1399.00|
|2008||SQL Server Native Client 10.0||2007.100.1600.22|
|2012||SQL Server Native Client 11.0||2011.110.2100.60|
|MySQL*||5.0||MySQL Connector/ODBC 3.5||3.51.29.00|
|MySQL Connector/ODBC 5.1||5.01.09.00|
|MySQL ODBC 5.2a/w Driver||5.02.02.00|
|OpenLink Virtuoso||4.5||OpenLink Virtuoso (4.5)||4.50.29.04|
|Oracle*||9i||Oracle ODBC Driver||9.02.00.65|
|10g||Oracle in XE||10.02.00.02|
|DataDirect 5.2 Oracle Wire Protocol||5.20.00.48|
|11g||Oracle in <oracle 11 home>||11.01.00.06|
|Pervasive PSQL||9.5||Pervasive ODBC Client Interface||9.50.77.02|
|SOLID Embedded Engine||4.5||SOLID ODBC Driver 4.5 - (ANSI)||4.50.00.68|
|SQL Anywhere*||9||Adaptive Server Anywhere 9.0||9.00.02.3137|
|SQLite*||184.108.40.206||SQLite3 ODBC Driver||0.86.00.00|
|Sybase*||12.5||DataDirect 5.1 Sybase Wire Protocol||5.10.00.81|
|OpenLink Lite for SQL Server (TDS) (32-bit)||5.20.76.00|
|15||DataDirect 5.2 Sybase Wire Protocol||5.20.00.13|
|Adaptive Server Enterprise||15.00.00.50|
|Text Files||-||DataDirect 5.2 TextFile (*.*)||5.20.00.20|
|Microsoft Text Driver (*.txt; *.csv)||4.00.6304.00|
|pass fair/issues failed/not
supported (32-bit, 64-bit)
*Extended metadata support
You must follow post FixPak installation instructions. See flash or section 1.3.5 in the FixPak Readme for detailed instructions.
SQL Error. Native Code: 0, SQLState: IM004, Return Code: -1 [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed
A workaround is to run the application as an administrator in order to connect to DB2 using the ODBC driver in Windows 7.
Tables are not listed in a Tables/Views comparison unless Remote Client/Server mode is used to connect to the database.
Driver crashes saving synchronized data. Fixed in newest releases of DataDirect ODBC driver.
Only one application can connect to the the embedded Firebird database at any one time. Note, however, that an application can have multiple connections to the same embedded database as long as all these connections are from the same instance of the application.
Solution: verify that no other applications are connected to the embedded repository database. You can use Windows Task Manager to scan for cmpdata.exe to ensure that only one instance of the application is connected to the embedded repository.
This error may also be due to another application using the embedded Firebird client (fbclient.dll) or if the database file does not exist.
If you want to have multiple applications connect to CompareData repository database at the same time, then you need to run Firebird as a Server and set up an ODBC data source for the repository database. You can download Firebird server from www.firebirdsql.com
This driver is distributed with CompareData and is used by CompareData to connect to its embedded repository. You can use this driver to compare/synchronize Firebird databases.
FrontBase has a fix build for the driver that addresses miscellaneous issues.
Issues with Java VM running out of memory when retrieving/synchronizing tables with large data.
Driver does not support SQLTables SQL_ALL_CATALOGS
SQLForeignKeys returns rows for another table with the same name as the requested table (but with different owner). Will be fixed in the next release of the Ingres ODBC driver.
Not supported. Matisse ODBC driver is ODBC-level 2.50 rather than level 3.5 required by CompareData.
Enter password all upper case when setting up application data source or leave password blank to have the driver prompt you for the password.
Various issues with synchronizing data.
Poor performance with deletes, inserts, and updates sql statements. If you are not going to write LOBs to Oracle you can improve the driver performance by unchecking the 'Enable LOBs' checkbox in the Oracle tabpage of the ODBC driver data source setup dialog.
Issue with parameter bind offset not getting used except for the first execution of a prepared sql statement. To avoid this issue, prepared statements are not used with this Oracle ODBC driver (SQORA32.DLL).
Oracle ODBC driver 9.x error, use ODBC Data Source Administrator to configure the data source ODBC driver. From the driver Workaround tab check 'Force Retrieval of Longs' option.
Poor peformance with catalog functions: SQLStatistics, SQLForeignKeys and SQLTablePrivileges (severe).
You attempted connect to an Oracle Database 10g Express Edition but you are already connected to another Oracle database using a different driver that has the same dll name as the Oracle 10g Express Edition driver dll (SQORA32.dll).
Solution: use the same driver when setting up ODBC data source for connecting to both Oracle databases.
For example, your client machine connects to an Oracle 9i Enterprise server but you also downloaed and installed Oracle 10g Express Edition on your client machine and you want to connect to both servers from CompareData at the same time:
Option to create public synonyms for repository tables was selected when the repository was created but option was not selected when repository was dropped leaving invalid repository public synonyms. To fix this issue drop the invalid repository public synonyms by running drop_synonym_xxx_ora.sql script located in Sql\Oracle folder of the application installation folder.
CompareData uses the dbms name, server name, database name, and login id to identify a data source. If you have two data sources for two different servers running on the same machine where the two servers are set up on different ports but both ODBC data sources servers are set up as 'localhost', CompareData will identify the two data sources as equivalent if you use the same login id for both data sources.
Workaround for now is to use a different login id or an equivalent but different server name, such as 'localhost' and '127.0.0.1'.
Driver ODBC level is 2.01 rather than level 3.5 required by CompareData.
Insert fails with return code 100 on executing an insert statement if the insert statement is a prepared statement and the previous execution of the statement encountered a server error. Workaround: in the driver ODBC setup window select 2 - Full for the Prepare Method in the Performance tab.
Issue with synchronizing dates. Month part of date gets decremented by 1. This is fixed in the latest update to the driver.
When setting the ODBC driver enable the No Quoted Identifers option in the driver setup dialog.
Various issues. Until these issues are fixed, it is recommended to use DataDirect Wire driver for Sybase instead.
In order to get resultset description for triggers and stored procedures/functions you must set the 'Enable Dynamic Prepare' option for the ODBC data source (Connection tab in the driver set up dialog)
Please see schema.ini for information about setting up text driver.
Driver does not allow text file names without extension or file extension is not allowed by default Q245407