Supported Databases in DatabaseSpy Print this Topic Previous Page Up One Level Next page

Home >  Introduction >

Supported Databases in DatabaseSpy

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

IBM Db2 for i 6.1, 7.1, 7.2, 7.3

Logical files are supported and shown as views.

IBM Informix 11.70, 12.10


MariaDB 10.2, 10.3

Microsoft Access 2003, 2007, 2010, 2013

Microsoft Azure SQL Database

SQL Server 2016 codebase

Microsoft SQL Server 2005, 2008, 2012, 2014, 2016, 2017,

Microsoft SQL Server on Linux

MySQL 5.0, 5.1, 5.5, 5.6, 5.7, 8.0

Oracle 9i, 10g, 11g, 12c

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

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

With Progress OpenEdge databases, there may be cases where a table cannot be deleted using the SQL script generated by DatabaseSpy. The workaround is to drop the table by entering a DROP TABLE statement in the SQL Editor window, instead of running the generated Database Structure Change Script.


The limitation originates in the fact that, in Progress OpenEdge, you cannot drop the first index created on the table, except by dropping the table. DatabaseSpy, on the other hand, attempts to remove all table constraints (which may be linked to the first index created on the table) before removing the actual table.

SQLite 3.x

SQLite connections are supported as native, direct connections to the SQLite database file. No separate drivers are required.

Sybase ASE 15, 16

Teradata 16


© 2019 Altova GmbH