Supported Databases in DatabaseSpy
The table below lists all the supported databases. 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.
Database | Notes |
|---|---|
Firebird 2.x, 3.x, 4.x | |
IBM DB2 8.x, 9.x, 10.x, 11.x | |
IBM Db2 for i 6.x, 7.4, 7.5 | Logical files are supported and shown as views. |
IBM Informix 11.70 and later | |
MariaDB 10 and later | |
Microsoft Access 2003 and later | 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 and later Microsoft SQL Server on Linux | |
MySQL 5 and later | |
Oracle 9i and later | |
PostgreSQL 8 and later | 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 |