AQT has been individually configured for the following databases:
| Database Explorer | Admin Component | ||
| Oracle | More | ||
| DB2 for LUW | More | ||
| DB2 for z/OS | More | ||
| DB2 for iSeries | More | ||
| Sybase ASE | |||
| Sybase Anywhere | |||
| Sybase IQ / SAP IQ | |||
| MS SQL Server | More | ||
| Informix | |||
| MySQL | More | ||
| Teradata | |||
| MS Access | |||
| MS Excel | |||
| SQLite | |||
| SAPDB / MaxDB | |||
| Pervasive.SQL | |||
| PostgreSQL | |||
| Interbase / Firebird | |||
| SQLBase | |||
| Netezza | |||
| NonStop SQL/MX | |||
| NonStop SQL/MP | |||
| Progress | |||
| CA-IDMS | |||
| Ingres | |||
| EXASolution | |||
| Redbrick | |||
| MariaDB | |||
| Snowflake | |||
| Redshift | |||
| YellowBrick |
If your database has an ODBC Driver, and this conforms to the normal standards, then you should be able to access your database using AQT.
Other databases AQT has been used against are:
