Which databases we work on

← Databases

We design, manage and migrate on MS-SQL, PostgreSQL, MySQL and MariaDB, Oracle, Firebird and Interbase, ElevateDB and DB2 for i on the AS/400. Below is what we actually do per platform — design, migration, reporting, or all three at once.

Updated on 28 August 2026

Server databases

MS-SQL Server
The most common target platform in a migration. Design, maintenance, reporting and setting up the backup.
PostgreSQL
The usual alternative without licence costs. Excellent as a destination for data from an older system.
MySQL and MariaDB
Widely used under web applications and webshops; also where integrations can keep their processing log.
Oracle
Present in larger environments. We work on it and connect to it, with an eye on what the licence permits.

Application and embedded databases

Databases that ship with an application rather than running on a server of their own.

Firebird and Interbase
Common under Delphi applications. Still maintainable, and migratable once requirements grow.
ElevateDB and DBISAM
Built into the application itself. Readable and transferable to a server database.
Microsoft Access
Fine for a single user, awkward once there are more. Moving to MS-SQL or PostgreSQL is then the logical step.
SQLite
Small, reliable and present everywhere. We use it where a full server would be overkill.

Particular platforms

DB2 for i (AS/400)
An ordinary relational database under an unusual system. Readable directly with the right driver; we have also migrated one to another platform.
Legacy file formats
dBase, Clipper, Paradox and the BDE do not strictly belong in this list, but they come out of the same cupboard.

In a migration the work is not the copying but the verification afterwards: do the record counts, data types, dates and accented characters match? We supply that comparison, so it is demonstrable that everything came across complete.

More on this →

Question not covered here?

Describe briefly what it is about and we will tell you what is possible.