The following table lists the database connection types supported for each platform.
Yes, with some limitations, see ADO.NET Support Notes
For a database connection to be possible, the required database drivers must be installed on the operating system, namely:
•For ADO.NET connections, the .NET Framework must be installed. Also, the ADO.NET provider of the database vendor must be installed if not already available on your operating system. Note that the ADO.NET providers of certain databases are not supported, see ADO.NET Support Notes.
•For JDBC connections, the JDBC drivers must be added to the CLASSPATH variable. Also, the JRE (Java Runtime Environment) or Java Development Kit (JDK) must be installed. This may be either Oracle JDK or an open source build such as Oracle OpenJDK. As an alternative to changing the CLASSPATH variable, you can add values to the Java class path by configuring the data source with the extend-classpath option.
•For ODBC connections, the ODBC driver of the respective database vendor must be installed.
The 32-bit or 64-bit platform of DiffDog Server should match that of the database driver.
PostgreSQL and SQLite connections are supported natively and do not require any drivers.
You can view at a glance all the database drivers detected on your machine by DiffDog Server by running the db-drivers command.
The following databases are supported. While Altova endeavors to support other databases, successful connection and data processing have only been tested with the databases listed below. If your Altova application is a 64-bit version, ensure that you have access to the 64-bit database drivers needed for the specific database you are connecting to.
Firebird 2.5.4, 3.0
IBM DB2 8.x, 9.1, 9.5, 9.7, 10.1, 10.5, 11.5, 11.5.7
IBM Db2 for i 6.1, 7.1, 7.2, 7.3, 7.4
Logical files are supported and shown as views.
IBM Informix 11.70, 12.10, 14.10
MariaDB 10.2, 10.3, 10.4, 10.5, 10.6.5
Microsoft Access 2003, 2007, 2010, 2013, 2016, 2019
At the time of writing (early September 2019), there is no Microsoft Access Runtime available for Access 2019. You can connect to an Access 2019 database from Altova products only if Microsoft Access 2016 Runtime is installed and only if the database does not use the "Large Number" data type.
Microsoft Azure SQL Database
SQL Server 2016 codebase
Microsoft SQL Server 2005, 2008, 2012, 2014, 2016, 2017, 2019
Microsoft SQL Server on Linux
MySQL 5.0, 5.1, 5.5, 5.6, 5.7, 8.0, 8.0.25, 8.0.28
Oracle 9i, 10g, 11g, 12c, 18, 19
PostgreSQL 8.0, 8.1, 8.2, 8.3, 9.0.10, 9.1.6, 9.2.1, 9.4, 9.5, 9.6, 10, 11, 12.1, 13, 14.1
PostgreSQL connections are supported both as native connections and driver-based connections through interfaces (drivers) such as ODBC or JDBC. Native connections do not require any drivers.
Progress OpenEdge 11.6
SQLite 3.35.5, 3.37.2
SQLite connections are supported as native, direct connections to the SQLite database file. No separate drivers are required.
Sybase ASE 15, 16
The following table lists known ADO.NET database drivers that are currently not supported or have limited support in DiffDog Server.
.Net Framework Data Provider for ODBC
Limited support. Known issues exist with Microsoft Access connections. It is recommended to use ODBC direct connections instead.
.Net Framework Data Provider for OleDb
Limited support. Known issues exist with Microsoft Access connections. It is recommended to use ADO direct connections instead.
Firebird ADO.NET Data Provider
Limited support. It is recommended to use ODBC or JDBC instead.
IBM Informix Data Provider for .NET Framework 4.0
Not supported. Use DB2 Data Server Provider instead.
IBM DB2 for i (iSeries)
.Net Framework Data Provider for i5/OS
Not supported. Use .Net Framework Data Provider for IBM i instead, installed as part of the IBM i Access Client Solutions - Windows Application Package.
.Net Framework Data Provider for Oracle
Limited support. Although this driver is provided with the .NET Framework, its usage is discouraged by Microsoft, because it is deprecated.
No ADO.NET drivers for this vendor are supported. Use a native connection instead.
No ADO.NET drivers for this vendor are supported.